ServerView ESXi Health Core Provider Version 10.80 Release Notes Copyright 2024 Fsas Technologies Inc. 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.1.3 Deinstallation 4.2 Configuration 4.3 Starting and stopping service 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 Health Core 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 Health Core 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 https://support.ts.fujitsu.com/IndexDownload.asp following "Software" "ServerView" "Operation" "Agents, Agentless Service & Providers" select Operating System VMware ESXi and on the ServerView Suite DVD. 1.3 Documentation The functionality of the ServerView ESXi Health Core Provider is documented in the manual "ServerView ESXi Health Core Provier" You will find this manual at https://support.ts.fujitsu.com/IndexDownload.asp following "Software" "ServerView" "Operation" "Agents, Agentless Service & Providers" select Operating System VMware ESXi 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 Health Core 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 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 o ServerView ESXi Health Core Provider are contained in one VMware Offline Bundle: - FJT-esx-8.0-FJT-svhcp_.-1OEM.800..zip Offline Bundle with the ESXi Health Core Provider for ESXi 8.0 o ServerView HTI driver, the VIB containing the kernel module for access to the HTI interface, are included in an additional offline-bundle: - FJT-esx-8.0-FJT-svshti-.-1OEM.800..zip Offline Bundle with the HTI interface for ESXi 8.0 Installation of the ServerView HTI driver is required for the corret functioning of ServerView ESXi Health Core Provider o ServerView ESXi Operations Manager Connector, the VIB supporting the connection with ServerView Operations Manager, are included in an additional offline-bundle: - FJT-esx-8.0-FJT-svomc-.-1OEM.800..zip Offline Bundle with the ESXi Operations Manager Connector for ESXi 8.0 Installation of the ServerView ESXi Operations Manager Connector is required only when the ESXi system is monitored by ServerView Operations Manager. 2.2 Hardware 2.2.1 Supported Hardware See https://support.ts.fujitsu.com/IndexDownload.asp 2.2.2 Required Hardware Not applicable. 2.3 Software 2.3.1 Supported Software (OS) See https://support.ts.fujitsu.com/IndexDownload.asp 2.3.2 Required Software Installation of the ServerView HTI driver is required for the corret functioning of ServerView ESXi Health Core Provider Optionally, the ServerView RAID Core Provider may be installed to enhance the mass storage management functionality. 3 Changes See https://support.ts.fujitsu.com/IndexDownload.asp 4 Product Installation, Configuration, Start-up When installing ServerView ESXi Health Core 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 Health Core Provider. ServerView ESXi Health Core Provider 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. Installation / Update Installation: (1) Copy the offline bundle to the ESXi system. (2) Login to ESXi Shell or SSH as root. (3) Execute the following command: esxcli software component apply -d [full path to .zip package] (4) Reboot the system. Checking the installed software: (1) Login to ESXi Shell or SSH as root. (2) Execute the following command: esxcli software component list Component Name of ServerView ESXi Health Core Provider: - FJT-svhcp (ServerView ESXi Health Core Provider) - FJT-svshti (ServerView HTI driver) - FJT-svomc (ServerView ESXi Operations Manager Connector) * FJT-svomc is required only when the ESXi system is monitored by SV Operations Manager. 4.1.3 Deinstallation In any case the ESXi system must run in the maintenance mode. (1) Login to ESXi Shell or SSH as root. (2) Execute the following command: esxcli software component remove -n Component Name of ServerView ESXi Health Core Provider: - FJT-svhcp (ServerView ESXi Health Core Provider) - FJT-svshti (ServerView HTI driver) - FJT-svomc (ServerView ESXi Operations Manager Connector) (3) Reboot the system. 4.2 Configuration Not applicable 4.3 Starting and stopping service After ServerView ESXi Health Core Provider has been installed, the service of ServerView ESXi Health Core Provider is started automatically with each system startup. For diagnostic purposes, it may be meaningful to explicitly stop and then restart the service. To start/stop ServerView ESXi Health Core Provider, you must log-in to the ESXi host as the root user and execute the commands. To start ServerView ESXi Health Core Provider service: /etc/init.d/FujitsuSVHCP start To stop ServerView ESXi Health Core Provider service: /etc/init.d/FujitsuSVHCP stop To restart ServerView ESXi Health Core Provider service: /etc/init.d/FujitsuSVHCP restart 4.4 Requirements for Security Configuration Not applicable 5 OS-specific Issues This section lists incompatibilities in ServerView ESXi Health Core 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 Not applicable 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 "PrimeCollect" a) Prerequisites: - SV ESXi Health Core Provider >=V10.70 - ServerView HTI driver >=V10.40 b) PrimeCollect data will be stored in a first datastore found by SV Health Core Provider. To change datastore on which Prime Collect data will be stored please set volumename parameter in [primecollect] section of /opt/FujitsuSVHCP/vital/etc/srvmagt/PrimeCollect.txt file. If there is no datastore in the ESXi system and "volumename" is empty, getting PrimeCollect failed. o Function "Driver Monitor" Prerequisites: - SV ESXi Health Core Provider >=V10.70 - ServerView HTI driver >=V10.40 o Function "Network Interface" Prerequisites: - SV ESXi Health Core Provider >=V10.70 - ServerView HTI driver >=V10.40 o Function "Power Operation (Graceful Reset / Power Off) on iRMC" a) Prerequisites: - SV ESXi Health Core Provider >=V10.70 - ServerView HTI driver >=V10.40 b) In order to execute Graceful Reset or Power Off on iRMC, the ESXi system must run in the maintenance mode. o Function "Monitoring by SV Operations Manager" a) Prerequisites: - SV ESXi Health Core Provider >=V10.80 - ServerView HTI driver >=V10.40 - SV ESXi Operations Manager Connector >=V10.80 - SV Operations Manager >=V10.50.02 b) The following functionalities are not supported yet. - Alarm - Test Connectivity