Fujitsu ServerView ESXi CIM Provider Version 9.80 Release Notes Copyright 2020 FUJITSU LIMITED All rights reserved Designations used in this document may be trademarks, the use of which by third parties for their own purposes could violate the rights of the trademark owners. Contents 1 General 1.1 Ordering 1.2 Delivery 1.3 Documentation 1.4 License Terms and Conditions 2 System Requirements 2.1 Delivery Units 2.2 Hardware 2.3 Software 3 Changes 4 Product Installation, Configuration, Start-up 4.1 Installation and Deinstallation 4.1.1 Installation with ESXi Installable and ESXi Embedded image 4.1.2 Installation of the Offline Bundle 4.2 Configuration 4.3 Startup and Shutdown 4.4 Requirements for Security Configuration 5 OS-specific Issues 5.1 VMware ESXi 6 Corrigenda of Product Documentation 7 Hints 1 General This Release Note is supplied together with the software deliverables on the ServerView Suite DVD and also available at support.ts.fujitsu.com/prim_supportcd/start.html following "Software Products" "ServerView" and "Agents and Provider". If one or more previous versions are skipped when this product version is used, the information from the Release Note (and README files) of the previous versions must also be noted. 1.1 Ordering ServerView ESXi CIM Provider are a component of the ServerView Suite. The ServerView Suite is supplied for every new PRIMERGY server and also available per subscription. Contact your Fujitsu sales representative for ordering details. 1.2 Delivery ServerView ESXi CIM Provider are supplied on the ESXi Installable and ESXi Embedded image. The Offline Bundles are also available online on the support pages of our Internet portal at http://ts.fujitsu.com/support following "Software" "ServerView" "Operation" "Agents and Provider" - select Operating System VMware ESXi and on the ServerView Suite DVD. 1.3 Documentation The functionality of the ServerView ESXi CIM Provider is documented in the manual "ServerView CIM Provider for Windows, Linux, and VMware ESXi" You will find this manual at http://ts.fujitsu.com/manuals following "x86 Servers" "Software" "ServerView Suite" "Operation" "ServerView Agents and Provider" The manuals may be supplemented by changes and extensions included in section 6 of this Release Note. See also the ServerView Suite data sheets available from the Fujitsu web site ts.fujitsu.com. 1.4 License Terms and Conditions ServerView ESXi CIM Provider are subject to the general terms and conditions of the Fujitsu software product use and service agreement. The ServerView Suite is licensed software bundled with the PRIMERGY server hardware. It must only be used in conjunction with Fujitsu's hardware, software or services. The conditions in the ServerView Suite End User Software License Agreement governing the copying and forwarding of the software to third parties, etc. must be observed. For further details see the End User License Agreement (EULA) on the ServerView Suite DVD. 2 System Requirements 2.1 Delivery Units ServerView ESXi CIM Provider are contained in one VMware Offline Bundle: - SVS-VMware-ESXi65-CIM-Provider-..zip Offline Bundle with the ESXi CIM Provider for ESXi 6.5 and 6.7 - SVS-VMware-ESXi70-CIM-Provider-..zip Offline Bundle with the ESXi CIM Provider for ESXi 7.0 Supplementary software, in particular the VIB containing the kernel module for access to the HTI interface are included in an additional offline-bundle: - fujitsu-hti-.-6.0.0-offline-bundle.zip Offline Bundle for ESXi 6.5 and 6.7 - Fujitsu-svshti_.-1OEM.700..zip Offline Bundle for ESXi 7.0 This supplementary software can only be used on systems equipped with at least iRMC S4. It supplies enhancements and the installation is not a requirement for the use of the CIM providers. 2.2 Hardware 2.2.1 Supported Hardware See http://ts.fujitsu.com/support/downloads.html 2.2.2 Required Hardware Not applicable. 2.3 Software 2.3.1 Supported Software (OS) See http://ts.fujitsu.com/support/downloads.html 2.3.2 Required Software Not applicable. 3 Changes See http://ts.fujitsu.com/support/downloads.html 4 Product Installation, Configuration, Start-up When installing ServerView ESXi CIM Provider, you must follow the information concerning installation in the documentation listed in section 1.3 as well as the information in this Release Note. 4.1 Installation and Deinstallation 4.1.1 Usage of ESXi Installable or ESXi Embedded image Fujitsu provides special versions of ESXi installable and ESXi embedded image including ServerView ESXi CIM providers. The ServerView ESXi CIM Providers are directly ready for use. 4.1.2 Installation of the Offline Bundle The Offline Bundle may be used for a direct update of a VMware ESXi system or may be loaded into the update repository of the vCenter Update Manager. Before you can install an update or patch from an ESXi host from the command line, you must have access to a machine on which you can run the VMware vSphere Command-Line Interface (vSphere CLI). For a detailed description of installation please see the documentation supplied by VMware. In any case the ESXi system must run in the maintenance mode. The installation will fail otherwise. After installation a system reboot must be performed to make the installation effective. 4.2 Configuration Not applicable 4.3 Startup and Shutdown Not applicable 4.4 Requirements for Security Configuration Not applicable 5 OS-specific Issues This section lists incompatibilities in ServerView ESXi CIM Provider with respect to previous releases or restrictions on the functions of the current release. NOTE: There may also be issues that apply to the PRIMERGY systems, their components and the operating systems. See corresponding README files. 5.1 VMware ESXi o CIM Provider Update might fail Although the server is running and CIM providers are working, server component states are not shown at the user interface of ServerView Operations Manager. The server might even be indicated as "not manageable". If this occurs the ESXi shell command enum_instances SVS_PGYHealthStateComponent root/svs will return only a single instance instead of a long list of instances. Cause The ServerView ESXi CIM Providers VIB installs files to the directory /etc/cim/svs_pgyeecd with the sticky bit being set. The files are used to keep information about provider activities and configuration across system reboot. The file "/etc/cim/svs_pgyeecd/registry" is essential for this purpose. Because the sticky-bit is set a file will be saved before system shutdown, and it will be restored after the system boot. Unfortunately this will be done also in the case the files have been changed by an update installation. Also a damaged file can be restored. Thus necessary data may be not available. The provider functionality is reduced. Resolution There are two possible ways to solve this issue. 1. Move default contents to configuration file "/etc/cim/svs_pgyeecd/registry" and restart SFCB. (1) Login to ESXi Shell or SSH as root. (2) Change to the directory /etc/cim/svs_pgyeecd. cd /etc/cim/svs_pgyeecd (3) Delete file named "registry", and replace it. rm registry cp registry.default registry (4) Do the same for other files with suffix ".default". Use them to replace the files without this suffix. (5) Restart SFCB /etc/init.d/sfcbd-watchdog restart 2. Remove ServerView ESXi CIM Providers completely and reinstall them again. o Remove ServerView ESXi CIM Providers (1) Login to ESXi Shell or SSH as root. (2) Remove the VIB esxcli software vib remove -n svscimprovider (3) Reboot the system o After Reboot reinstall ServerView ESXi CIM Providers and reboot the system once more. (1) Login to ESXi Shell or SSH as root. (2) Move offline-bundle for installation to the local file system. (3) Install offline-bundle. esxcli software vib install -d //SVS-VMware-ESXiXX-CIM-Provider-x.xx.xx.zip (4) Reboot the system. This issue is also described in kb article 2149733: https://kb.vmware.com/s/article/2149733?lang=en_US o Update Installation of SV ESXi CIM Provider >=V8.50 File /etc/cim/svs_pgyeecd/registry was cleaned up in V8.50 (there were no functional changes). An update installation will preserve the old file (= normal ESXi behavior for this kind of file) A complete reinstallation is required for the change to be effective: (1) remove old version of ServerView ESXi CIM Providers (2) reboot the system (3) install new version o New-/Update-Installation of HTI Support V8.20.04/V9.00.06 on ESXi V6.7 via vSphere Update Manager V6.7 Installation not possible --> Status: Not Applicable Workaround: use command esxcli o Upgrading CIM Provider <=9.30 for ESXi 7.0 Since 9.40 svshti-lib vib has been removed from HTI driver and integrated into CIM Provider. CIM Provider will return error during upgrade when the HTI driver <9.40 will be installed on the system. To avoid upgrade failure HTI Driver must be upgraded first, it will remove svshti-lib from system. After driver upgrade CIM Provider can be ugraded without dependency error, svshti-lib will be installed again as a part of CIM Provider component. o Upload of HTI Support V9.00.06 to vSphere Update Manager Error message: Invalid vendor code fjt in patch metadata, another vendor code with different capitalization already exists in database. Check the Update Manager log files for more details Occurence #1 Repository of VMware Update Manager (Appliance) contains certified version (T50) of SV ESXi CIM Provider - index.xml: FJT => It is not possible to upload HTI Support V9.00.06 - index.xml: fjt Occurence #2 Repository of VMware Update Manager (Appliance) contains HTI Support V9.00.06 - index.xml: fjt => It is not possible to upload certified version (T50) of SV ESXi CIM Provider - index.xml: FJT Workaround: use command esxcli on ESXi host If a reset of the database is necessary, see kb article 2147284 (Resetting VMware Update Manager Database on a vCenter Server Appliance 6.5 or 6.7): https://kb.vmware.com/s/article/2147284?lang=en_US 6 Corrigenda of Product Documentation This section contains corrigenda for the product documentation as listed in section 1.3. o Not applicable. 7 Hints This section gives general hints, for example, how to deal with common issues. o Function "Driver Monitor for ESXi" Prerequisites: - Inband: SV ESXi CIM Provider >=V7.30.06 - Out of band: a) iRMC S4 FW >=8.64F SV ESXi CIM Provider >=V7.31.06 HTI Support for SV ESXi CIM Provider >=V7.31.05 b) iRMC S5 SV ESXi CIM Provider >=V8.00.15 HTI Support for SV ESXi CIM Provider >=V8.00.15 Supported by CIM Clients, for example: - SV OM Win >=V8.00.03 - SV OM Lx >=V8.10.01 - SV Integration Pack for vCenter >=V2.5.3 Lifetime of Driver Monitor Log/Status ends with stop of sfcb Problem with ServerView ESXi CIM Provider <= 9.00.18: - no Driver Monitor data Reason: - Incompatible change in ESXi 6.5 U2 (11925212-Fujitsu-v422-1-2019-0213-133035) concerning command lspci. o Function "Network adapter, link-up/-down status" Prerequisites: - iRMC S4 FW 9.60F or higher - SV ESXi CIM Provider >=V7.31.06 - HTI Support for ServerView ESXi CIM Provider V7.31.05 or higher o Function "monitor out-of-band Optical Power of NIC-cards" Intel D2755 a) Prerequisites: - SV ESXi CIM Provider >=V8.30.08 b) Intel D2755 (TFS 33100): - ESXi >=6.5: native Intel drivers have to be replaced by legacy (vmklinux based) drivers: replace ixgben by net-ixgbe Intel X710 a) Prerequisites: - SV ESXi CIM Provider >=V9.00.06 - Firmware >=6.00 b) Different names for different ports - Port 0 of X710-DA2 and X710-DA4 can be distinguished - Port 1 to 3 have the same PCI SubDeviceID 0000 and cannot be distinguished: shown as X710-DAx. o Function "Software Inventory support for eLCM dedicated offline update" Prerequisites: - SV ESXi CIM Provider >=V8.30.08 - PNI revision B minimum (available since PRIMERGY M2 family) - Supported Controller Broadcom PSAS CP400e / CP400i / CP420i Fibre Channel Emulex PFC EP LPe16000 1x 16Gb / LPe16002 2x 16Gb / LPe31000 1x 16Gb / LPe31002 2x 16Gb Fibre Channel QLogic PFC EP QLE2670 1x 16Gb / QLE2672 2x 16Gb / QLE2690 1x 16Gb / QLE2692 2x 16Gb Intel LAN and more Supported by CIM Client: - SV Integration Pack for vCenter >=V3.0 o Function "Support of SV ESXi RAID Core Provider" Prerequisites: It is strongly recommended to use corresponding versions. - First release: SV ESXi CIM Provider >=V8.00.15 SV ESXi RAID Core Provider >=V8.00.11 - <= V9.30.xx First and second digit (n.nn) must be equal for both software packages: SV ESXi CIM Provider Vn.nn.xx SV ESXi RAID Core Provider Vn.nn.xx - >= V9.40.xx: The version numbers can be different if the versions are V9.40 and newer. SV ESXi CIM Provider >=V9.40.xx SV ESXi RAID Core Provider >=V9.40.xx Supported by CIM Clients, for example: - SV Integration Pack for vCenter >=V2.6.6 - SV Integration Pack for Nagios >=V3.40.00 o Function "PrimeCollect for ESXi based server" a) Prerequisites: - iRMC S5 FW >=2.20P - SV ESXi CIM Provider >=V8.51 - HTI Support for ServerView ESXi CIM Provider >=V8.20.04 b) Runtime of cronjob (once a day, UTC by default): - V8.51: 2:00 AM - >=V9.00: 11:23 PM - V9.00.18: no cronjob for all releases of ESXi 6.5 The time is chosen arbitrarily so as not to collide with other cron jobs. The cron job for writing VM Support archive can be removed by calling /etc/init.d/svshti stop. Please note: This modification is temporary, it only lasts until the next reboot. c) Content of PrimeCollect archive: - V8.51: default settings of vm-support are used - >=V9.00: Hardware, Configuration, Storage, Network, Logs d) The system-storage on the hard-disk will be used to store VM Support archive. A symbolic link /tmp/PrimeCollect_Data.tgz points to the newly created archive. e) To change datastore on which Prime Collect data will be stored please set volumename parameter in [primecollect] section of /etc/cim/svs_pgyeecd/cim_config.ini file. Otherwise default location will be used. Restart sfcbd in order to introduce changes: /etc/init.d/sfcbd-watchdog restart Restrictions for ESXi 6.5 + SV ESXi CIM Provider >=V8.51 - Problem: At run-time of cron job a lot of messages "MemSched...Admission failure in path: init/python..."" are written to /var/log/vmkernel.log. This is a bug in ESXi 6.5 (VMware Support Request #19144512104). Workaround: (1) Stop cron job for writing vm-support bundles via /etc/init.d/svshti or use SV ESXi CIM Provider V9.00.18 (no cron job for ESXi 6.5) (2) Stop has to be repeated after every reboot (3) Manual execution of shell-script /opt/fts/bin/prcoll-vm-support.sh if vm-support for PrimeCollect is needed Solution: (1) Update ESXi CIM Provider to version => V9.00.18. (2) Install "Enable PrimeCollect for ServerView ESXi CIM Provider" V9.20-08 offline bundle which is applicable to CIM Provider from version V9.00.18. Installation: (1) Copy offline bundle to ESXi host. (2) Run command: esxcli software vib install -d / (3) Reboot ESXi host, which is mandatory for this solution to work. - Problem: High sporadic crash of python at runtime of cron job (does not harm system) o Profile SVS PGY Disk Drive Lite Problem: no data is provided Root cause: SV ESXi RAID Core Provider V8.51.02 - incompatible changes in Storage Device Tree Assumed impact for CIM-Clients (e.g. vCenter Plug-in): Data can't be read out for Storage Workaround: Use SV ESXi RAID Core Provider <= V8.50 or >=V9.00.02 o Sporadic problem "hang-up of HTI interface within iRMC S5" if iRMC S5 FW 2.41P is rebooted causes: - Functionality of HTI Support for ServerView ESXi CIM Provider can't be used anymore - After ~30 Min. after occurrence: . every 2 minutes log-entries are written by HTI Support for ServerView ESXi CIM Provider to /var/log/vmkernel.log: ... fujitsu-hti: hti_send_message could not write message register. The message queue is full ... . ESXi host might become very slow / login hardly possible -> not Manageable Workaround: (1) Reboot of iRMC S5 (2) or use FW <2.41P or >=2.42P o During boot of the system and on the systems with controllers which support Optical Power measurements entries: "WARNING: ... sfcb-svs_pgyeec: Error cloning thread: -1 (bad0117)" are written to /var/log/vmkernel.log. Affected controllers: - Intel X710 - Fujitsu D2755 Causes: - Fault in third party library used to provide optical power values. INTEL confirmed that this issue comes from the INTEL LAN SDK library they provided for the CIM provider. But as it is only a warning and no serious issue behind INTEL does not provide a new SDK version. Solution: In the version 9.30 functionality to provide Optical Rx and Tx power has been disabled by default. To enable functionality it is needed to put following line in file "/etc/vmsyslog.conf": OPTICAL_POWER_FEATURE = true and restart sfcb: /etc/init.d/sfcbd-watchdog restart Starting from the version 9.70 the way of enabling functionality described above changed. Currently to enable Intel Nal Support it is needed to set 'Support' parameter on true in [IntelNalSupport] section of /etc/cim/svs_pgyeecd/cim_config.ini file. Restart sfcbd in order to introduce changes: /etc/init.d/sfcbd-watchdog restart It will enable providing Optical Rx and Tx power values but also warning message will be printed to /var/log/vmkernel.log. Workaround: If the vaules are needed also ESXi log filtering mechanism can be used. (1) Add following line into file /etc/vmware/logfilters: 0 | vmkwarning | .*Error cloning thread: -1.* (2) Add in a file /etc/vmsyslog.conf in the section [vmsyslog]: enable_logfilters = true (3) Use command: esxcli system syslog reload o During the stop phase of sfcb high sporadic crashes of sfcb-svs_pgyeec and sfcb-LSIESG_SMI occur. No harm to system o IPMI Software Watchdog can be used for system monitoring only to a limited extent. There must be the following settings: Action on Expiration: Continue Timeout: >= 4 minutes Any setting made by the user will be reset automatically if it is not consistent with these restrictions. o Qlogic adapter QLE2560/QLE2562 Firmware version could not be provided if SubDeviceId is missing in the PNI data. o PRIMEQUEST a) EECD Provider is not reloaded, if the firmware of the BMC has changed. b) There is no automatic retrieval and provision of the system ip address to the MMB to support automatic detection in the SVOM for ESXi. Therefore the IP address has to be set in the SVOM manually. Up to now this is accepted as restriction. c) PRIMEQUEST 3400E / 3400L / 3400S / 3400S Lite / 3800E / 3800L Requirements: - Unified FW package >17102 o Blade Server In ESXi the first kernel interface which is called vmk0 is the only interface with a physical MAC address. This means that only the IP addresses of this Interface can be directly assigned to a physical LAN port. The deactivation of the interface vmk0 may cause problems for blade servers, because there will be no IP address which can be assigned to one of the MAC addresses configured by the Management Blade. This may inhibit the system discovery by the Serverlist service of the ServerView Operation Manager. o ESXi V6 High overload (caused by (too many) CIM Clients) may cause monitoring problems. Workaround: Please restart sfcb o ESXi 6.5, CIM Indications Firewall in ESXi 6.5 blocks the delivery of CIM indications because lacking an appropriate rule. This is a bug in ESXi and accepted by VMware (PR#1742025). Workaround: An additional add-on VIB has been issued by Fujitsu: Add-on for ServerView ESXi CIM Provider V7.31.06, SW-ID: 1174284 The installation of the VIB adds the needed firewall rule. The VIB is available at the same site where the CIM provider can be obtained. Not necessary with ESXi 6.5 >= Update 1 build 5969303 o ESXi 6.5 + Add-on for ServerView ESXi CIM Provider Installation sequence for "Add-on for ServerView ESXi CIM Provider": - Add-on for ServerView ESXi CIM Provider - ServerView ESXi CIM Provider De-Installation sequence if "Add-on for ServerView ESXi CIM Provider" is installed: - Add-on for ServerView ESXi CIM Provider - ServerView ESXi CIM Provider o ESXi 6.5, Monitoring of events via CIM Clients Prerequisites - ServerView Operations Manager Win/Lx: V7.20.08 or higher - SV Integration Pack for vCenter V2.5 or higher o ESXi 6.7, Monitoring via ServerView RAID Manager Win/Lx Problem: crash of sfcb-CIMXML every minute Fix in: - ServerView RAID Manager Win/Lx >=V6.6.10 o ServerView Operations Manager for administration of ESXi servers: recommended: >= V8.41 o ServerView Operations Manager requires a valid user ID with "Administrator role" in order to authenticate itself when retrieving information from an ESXi system. o No HDD information for ESXi shown in SV Operations Manager o Information of Power Supply not fully supported by SV Operations Manager concerning Server Blades