Fujitsu Limited ServerView Operations Manager Version V10.30 02-Jun-2023 Release Notes Copyright (C) 2023 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 WARRANTY DISCLAIMER THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED WITHOUT ANY WARRANTY TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE OPEN SOURCE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. SEE THE APPLICABLE LICENSES FOR MORE DETAILS. 1. General 1.1. Ordering 1.2. Delivery 1.3. Documentation 1.4. License Terms and Conditions 2. System Requirements 2.1. Delivery Unit 2.2. Required Hardware 2.3. Required Software 2.3.1. Operating System 2.3.2. Web Browser 2.3.3. SQL database: 3. Changes 3.1. Main changes 3.2. Obsolete Functions 3.3. Incompatibilities with other Delivery Units 3.4. Upgrade 4. Products Installation and Configuration 4.1. Installation 4.1.1. All systems 4.1.2. Windows 4.1.2.1. Installation Prerequisites 4.1.2.2. Installation 4.1.2.2.1. Silent installation: 4.1.2.3. Terminal Server/Remote Desktop Services installation mode 4.1.2.4. Upgrading 4.1.2.4.1. Rollback to old ServerView version 4.1.2.5. Troubleshooting / Known Problems for installation on Windows 4.1.2.6. Configuration on Windows 4.1.2.6.1. Network Protocols for SQL Server Express installations 4.1.3. LINUX 4.1.3.1. Installation Prerequisites 4.1.3.2. Installation 4.1.3.3. Adaptation of configuration parameters 4.1.3.4. Effects of ServerView Operations Manager on system files on Linux 4.2. Configuration on Linux and Windows 4.2.1. User management 4.2.2. JMX port 4.3. Uninstall 4.3.1. Windows 4.3.2. Linux 5. Product Start-Up 5.1. Windows 5.1.3. Start problem with file C:\Program 5.1.4. Configuration of SNMP service 5.1.5. Changes of Computer Name, Domain/Workgroup membership, IP Address or Tomee service account 5.1.6. Adding server to empty list after system restart 5.2. Linux 5.2.1. Keyboard Navigation with Linux Mozilla browser 5.2.2. Event Manager / Receipt of traps 5.2.3. Configuration of libvirtd 6. Hints 6.1. Common 6.1.4. Unified RBAC 6.1.4.1. User with role being member of a group with role 6.1.5. Security 6.1.5.1. Updated SSL/TLS configuration of Application Server 6.1.5.2. Disabling new security features in SVOM. 6.1.6. SNMP 6.1.6.1. Unsuccessful browsing with SNMPv3 enabled 6.1.6.2. User's credentials for SNMPv3 6.1.6.3. CMS visibility in SVOM 6.1.6.4. Notes on changing global configuration of SNMP on Linux 6.1.7. Browsers 6.1.7.1. Proxy server problem 6.1.8. Language support 6.1.8.1. ServerView Operations Manager and ServerView Agent compatibility in scope of non-English languages support 6.1.9. System-related 6.1.9.1. Removal of trace files (Windows) 6.1.10. SVDBServer process 6.1.11. Configuration of libvirtd for XEN and KVM 6.1.12. SELinux/AppArmor 6.2. ServerView Event Manager 6.2.1. Broadcast Forwarding 6.2.2. Event Log Forwarding 6.2.3. Forwarding traps to management stations 6.2.4. SMTP Mail forwarding 6.2.4.1. Supported SMTP Authentication methods 6.2.4.2. SMTP Mail Forwarding in Linux 6.2.5. Servers send trap "Unauthorized message received" 6.2.6. Forwarding to executable on Windows 6.3. ServerView RAID 6.3.1. Security Settings in Internet Explorer 11 6.4. Networking 6.4.1. Network Notes 6.4.2. Tomee and rarely used ports 6.5. Database Server and Database Related Notes 6.5.1. Windows 6.5.1.1. Database backups - Shrinking logs on Windows 6.5.1.2. Setting SQL Server memory option on Windows 6.5.2. Linux 6.5.2.1. Reuse of dumps on Linux 6.5.2.2. Handling of large database server log on Linux 6.5.2.3. Changing from Local Database Server to Remote Database Server and vice versa on Linux 6.5.2.4. Database user for PostgreSQL 6.5.2.5. Crash of database server 'postgresql' 6.5.3. Remote SQL Server/PostgreSQL 6.6. VME 6.6.1. General notes 6.6.2. CIM provider version visibility 6.7. Threshold Manager 6.8. User Management 6.8.1. Role assignment 6.8.2. Backup and Restore of ApacheDS User Configuration 6.8.3. Changing group type in Active Directory from Distribution to Security 6.9. ServerView Download Service 6.10. Update Management (including Download Manager) 6.11. Diagnostics data collection 1. General This Release Note is a summary of the major extensions, dependencies and operating information with respect to ServerView Operations Manager 10.30 (SVOM) under the Windows and Linux operating system. If one or more previous versions are skipped when this product version is used, the information from the Release Notes of the previous versions must also be noted. 1.1. Ordering ServerView Operations Manager 10.30 is shipped on the PRIMERGY/PRIMEQUEST ServerView Suite DVD together with a PRIMERGY/PRIMEQUEST server. There is no license needed and the software can be downloaded for free from the internet (also see chapter 1.2) ServerView Operations Manager 10.30 is subject to the general terms and conditions of the Fujitsu software product use and service agreement. 1.2. Delivery The files are supplied on the PRIMERGY/PRIMEQUEST ServerView Suite DVD, which is included in the ServerStart package. This DVD is also available as an .iso image and as online version. Link to the [http://support.ts.fujitsu.com/prim_supportcd/start.html 1.3. Documentation The documentation can be downloaded free of charge from the Internet. You will find the online documentation on the download area of the Fujitsu Technical Support pages. To download the documentation, proceed as follows: - Visit [https://support.ts.fujitsu.com/IndexDownload.asp?PaOpenTab=manuals]. - Select the Select a new Product button. - Select Browse For Product. - Under Software (product line) - ServerView (product group) - Operation (product family) select the appropriate product. - Under Selected operating system, select OS Independent (BIOS, Firmware, etc.). - Select the Documents tab. 1.4. License Terms and Conditions The Software is subject to the general terms and conditions of the Fujitsu-software product use and service agreement Third-party Software incorporated in this product is listed in the file THIRDPARTYLICENSEREADME.txt shipped with this software. License texts are included there. 2. System Requirements 2.1. Delivery Unit ServerView Operations Manager 10.30 2.2. Required Hardware Processor: 2 x 2 GHz and above, Dual-Core CPU is sufficient. Memory: 4 GB RAM Free space on HD: more than 10 GB Hayes compatible modem (if pager requested) Graphics: 1024px horizontally and 800px vertically minimum, recommended 1280x1024, 32bit colors. These values represent a minimum requirement that may increase depending on the amount of data and the application used. 2.3. Required Software 2.3.1. Operating System Windows Server 64bit: 2012, 2016, 2019 or 2022 LINUX SuSE 64bit: SLES12 SP4, SLES12 SP5, SLES15 SP2, SLES15 SP3, SLES15 SP4, SLES15 SP5 RedHat 64bit: RHEL 7.8, RHEL 7.9, RHEL 8.4, RHEL 8.5, RHEL 8.6, RHEL 8.7, RHEL 8.8, RHEL 9.0, RHEL 9.1, RHEL 9.2 SELinux is supported only for RHEL7.8 and newer Please regard that free licenses with restricted functionality or evaluation versions for systems like ESXi are not fully supported. Network: TCP/IP protocol and Simple TCP/IP services and SNMP service 2.3.2. Web Browser Recommendation for browser usage: Windows: Mozilla Firefox ESR 68 or higher version Mozilla Firefox 75 or higher version Chrome 83 and higher version Microsoft Edge Linux: Mozilla Firefox ESR 68 or higher version Mozilla Firefox 75 or higher version Note: Please regard that cookies have to be allowed. So InPrivate/Incognito Browsing is not supported! When using a Firefox browser make sure that third-party cookies are allowed if you use custom settings for history. Internet Explorer: It is necessary to add the ServerView sites domain to your list of trusted sites. To do this, follow these steps (description for IE): Under "Tools" menu (on the right side of toolbar), select "Internet Options" Click "Security" tab Click "Trusted Sites" checkmark icon Click "Sites" button Uncheck "Require server authentication" box, unless you specifically want IE7 to confirm https connection requests Enter a site domain into the "Add this website to the zone" text field (e.g. https://sanfrancisco.swdev.mch.fsc.net) Click "Add" button Click "Close" button 2.3.3. SQL database: Windows: MS SQL 2014 Express SP3 (is installed by ServerView setup). External databases can be used: MS SQL Server 2019 Express, Standard, Enterprise MS SQL Server 2017 Express, Standard, Enterprise MS SQL Server 2016 Express, Standard, Enterprise MS SQL Server 2014 Express, Standard, Enterprise MS SQL Server 2012 Express, Standard, Enterprise If no suitable SQL Server is pre-installed on the system, SVOM setup will install an SQL Server 2014 Express edition on this OS version. Please regard that for configurations of 200 or more servers in server list SQL Server Express is not recommended. Please use SQL Server Workgroup/Standard/Enterprise instead For remote SQL Server no Express edition is supported. Linux: None (PostgreSQL is installed automatically from operating system's package repository). 3. Changes This section describes extensions and improvements of ServerView Operations Manager 3.1. Main changes V10.30 - Support RHEL 9.2 - Support RHEL 8.8 - Support SLES15 SP5 - SSL update (3.0.9) - Upgrading Spring Framework - Upgrading Apache Tomcat/Apache Commons FileUpload (CVE-2023-24998) V10.20 - Logging testing spript implementation - Update Agent build automation for Linux - Support RHEL 9.1 - Support RHEL 8.7 - Extending Cmscollect V10.10 - Support for SLES15 SP4 - Support for Windows Server 2022 IoT Storage - OpenSSL update 1.1.1q - Zlib update 1.2.12 V10.01: - Drop support Rhel 8.2 - Drop support Rhel 8.3 - OpenSSL version 1.1.1n update - Update RemoteConnector to 64-bit on Windows - Support for RHEL 8.6 - Support for RHEL 9.0 V10.00: - Adjust SVOM to use official PostgreSQL instead of custom built - SVOM Windows for 64 bit V9.80: - Edge browser support - TLS 1.3 - OpenSSL version 1.1.1l - RHEL 8.5 V9.71: - Bugfixes V9.70: - Drop support RHEL 7.6 - Improvements for SVOM - OpenSSL version 1.1.1k - RHEL 8.4 support - SLES15 SP3 support - Support TLS1.3 - Windows Server 2022 support - Upgrade embedded Java Runtime to version 8u292 V9.60: - Adding missing help buttons in SVOM V9.50: - Support for RX2530 M6/RX2540 M6 - Support for CX400/2550/2560 M6 - RHEL 8.3 support - Support for new OpenSSL 1.1.x - Option for disabling mail forwarding for Inventory and Report Manager V9.40: - SQL Server 2017 and Server 2019 Support - Help buttons functionality - Implement plugin support (SVIM, Fabric Manager) - E-track ID implementation for SVUM - Change layout for Archive Manager - Server Configurator V9.30: - RHEL 7.8 - SVOM Support - RHEL 8.2 - SVOM Support - Create new build environment for SVOM project (only for development) - SVRAID Storage Info Support in SVOM - Verify OWASP report and take necessary actions to secure SVOM - Reimplement StorMan View in SVOM so that it works with Mozilla and - Chrome (HTML5) - Customer specific extension for other languages for SVOM/UM - Angular change version from 6 to 8 - OpenSSL version 1.0.2u - Presentations for reports (inventory manager) V9.20: - HTML5 based user interface for SVOM -- Step 3 - OpenSSL version 1.0.2t - Update SQL 2014 SP2 to SP3 V9.10: - HTML5 based user interface for SVOM - Step2 - RAID-View - enhancements - Automatic service mail (Event configuration) - New OS: RHEL 7.7 - New HW: RX1330 M4 - New HW: TX1330 M4 - New HW: TX1320 M4 - ServerList of SVOM - Step2 - OpenSSL version 1.0.2s - New OS: SLES12 SP5 - New OS: RHEL 8.1 V9.02: - New OS: RHEL 8.0 - New OS: SLES15 SP1 - Improvements and bug fixing V9.01: - New HW: RX2520 M5 - New HW: TX2550 M5 - OpenSSL version 1.0.2r V9.00: - New HW: RX2530 M5 - OCP - New HW: RX4770 M5 - New HW: RX2540 M5 - New HW: RX2530 M5 - New HW: RX2520 M5 - New HW: TX2550 M5 - HTML5 based user interface for SVOM - New DB: PostgreSQL DB v10/11 for Linux based SVOM V8.51: - New OS: RHEL 7.6 - New OS: SLES 12 SP4 - OpenSSL 1.0.2.p - Scripts for silent SVOM install V8.50: - SNMPv1-v3 in parallel - New HW: TX1320 M4, TX1330 M4, RX1330 M4 - New OS: W2K19 - SQLServer 2016 V8.41: - New OS: SLES 15 - New OS: RHEL 6.10 - New HW: Eternus AF V8.40: - Agentless management - support RAID.MIB of iRMC - Quality and stability improvements - Integration of SV-RAID - support different kind of UI - Integration of new ASETEK CDU MIB - Integration of new WFM MIB - New HW: RX2530 M4 (Cascade Lake/AEP) V8.30: - Improvement of VME Service (Maintenance) - Quality and stability improvements - Solving remaining issues of JavaWebStart Migration - Support ISM 1.5d - Support of OpenSSL v.1.0.2_m - SSV - Conditional display of PSU and fans locations - New OS: RHEL 7.5 V8.21: - New HW: - - PQ 3800E - - PQ 3400E/S/S-Lite - - TX2550 M4 V8.20: - Solving problems with certain virus-scanners when installing SVOM - OpenSSL version 1.0.2l - Quality and stability improvements - Solving issues of Java WebStart Migration - Test automation part 1 - automated SVOM installation (silent and GUI - versions) - Stabilization and solving PRIMEQUEST issues - New OS: - - SLES12 SP3 - - RHEL 7.4 - New HW: - - PRAID Support EP440i/EP540i - - RX2520 M4 - - CX400 M4 V8.10: - Single System View -- measuring units - Phase out pictures for Rack-/Tower-servers - SVOM can install SQL Express version on server where SQL full versions are already installed - Improve AD integration in very big customer enviroments in terms of login speed (SAP) - For ESXi based servers show SEL messages, root cause and problem resolutions - New OS: - - SLES 12 SP1 - - SLES 12 SP2 - - RHEL 6.9 - New HW: - - RX2530 M4 - - PRIMEQUEST 3800B - - RX2540 M4 - - CX400 M4 - - RX2510 M2 8xSFF - SVOM Support - - SCM: bugfixes V8.00: - Implementation of applet free SVOM - Java WebStart - New feature: improved installation of SVOM on Linux - Removal of SC.MIB usage - Sustaining: Regular update of the support of StorMan - support of StorMan v7.0.1 - Security: Configuration of ciphers used in SVOM with Apache DS - Phasing out pictures for Rack-/Tower-servers - Enhancement of Base Configuration Wizard - E-mail forwarding to Service Provider - add macro server-ID - Presentation of data from driver monitor for ESXi nodes - New hardware supported: - - RX1330 M3 - - TX1330 M3 - - TX1320 M3 - - TX1310 M3 - - RX2530 M4 - - RX2540 M4 - - JX60 S2 - - Controller QLogic QL45212-2x25Gb - SCM: - - Added feature for SVIM to keep SCM main window always on top (when called with command line parameter "alwaysOnTop=true") V7.20: - New feature: Improved installation of SVOM on Linux - Sustaining: Integration of MIB (RACK PDU from Emerson) - Enhancement: iRBAC -- Authorize user with AD-account by role assignments contained in the local OpenDJ - Sustaining: Support of Microsoft SQL Server 2014 Express on all supported Windows Server editions - Security: Configuration of ciphers used in SVOM with TomEE - New OS: SLES 12 - New feature: Possibility of configuring additional Active Directory server - New OS: Windows Server 2016 - New HW support: TX1310 M3, TX1320 M3, TX/RX1330 M3, RX2530 M4 V7.11: - Implementation: Support of Java 8 with SVOM (server side java) - New OS: RHEL V7.1 - New OS: RHEL 6.7 - New OS: SLES 11 SP4 - Support for new database: SQL Server 2008 R2 Express SP3 - SCM changes: - - Added new page "iRMC SNMP Service" with general and SNMPv3 settings - - Added "Attach OS stop screenshot" option on page "iRMC Mail Format" - - Added options "Send FQDN with EHLO..." and SSL on page "iRMC > EMail Alerting". Page renamed to "iRMC EMail Alerting (SMTP)" - - Added "SNMPv3 Configuration" and "Extra SMS eMail subject" on page "iRMC User Management". Option "Account enabled" is now "IPMI user enabled". - - New page "iRMC Syslog Service" - - Supports all new systems (like Agents for Windows V7.20.18) - New HW: - - RX4770 M3 - - CELSIUS R940 - - CELSIUS C740 - - CX1640 M1 (CX600 M1) - - RX2510 M1 - - RX2510 M2 - - RX2560 M2 / TX2560 M2 - - PQ2800 B3 - - RX2530 M2 - - RX2540 M2 - - RX1330 M2 - - TX1330 M2 - - TX1320 M2 V7.10: - New feature: authorize an user with AD-account by role assignments contained in the local OpenDJ. - Single System View - locate function for agentless systems - New feature: Single System View - progress bar for ESXi based servers - Sustaining: Support SQL Server 2014 - Implementation: SNMPv3 support for SVOM - Sustaining: Support of PostgreSQL Database V9.2 - Maintenance: Migration from OpenDJ to Apache DS - NG: Cluster awareness of update management for BX Systems - New feature: Event forwarding using SMTP - Integrity of e-mail content - New feature: Liquid cooling - Enhancements in Event Management - Enhancements in User Management - Sustaining: Support of Xen on SLES 12 - Sustaining: Support of SSLv3/TLS vx.x V7.02: - New HW: PRIMEQUEST 2800 E2 - New HW: PRIMEQUEST 2800 B2 - New HW: PRIMEQUEST 2400 E2 - New HW: RX4770 M2 - New HW: JX40S2 - New HW: SX131 M1 (Storage model of the TX1310 M1 - Celsius C740 -- Support in SVOM - New feature: Port of SCS Service (Linux) to 64-Bit - Implementation: Support of Java 8 with SVOM (Client Side) (for - remarks on using Java 8 see section Error! Reference source not found. V7.00: - New HW: BX2560 M1 - New OS: RHEL V7.0 - SA/CR 233496172: Customer wants to change the Group type in AD from - Distribution to Security - Sustaining: SVOM Serverlist- Adaptation to SC2.MIB - Celsius R940 - Support in SVOM - Sustaining: Improvement of database setup - New feature: Export of SVOM serverlist using CLI - Sustaining: Improvement of test connectivity check for ESX based - servers - Sustaining: monitoring correct status of Hyper-V replicas in SVOM - Next Gen: Discovery and monitoring of agentless servers - New HW: CX2550 M1 - New HW: CX2570 M1 - New HW: CX400 M1 - New feature: SE Linux support - New HW: RX2530 M1 - New OS: RHEL 5.11 - New HW: BX2580 M1 - New HW: RX2540M1 SFF - New HW: RX/TX2560M1 V6.31: - New HW: RX1330 M1 - New HW: TX1320 M1 / TX1330 M1 - Inventory Manager - Adaptation to new ESX (previous: ESXi) CIM - Providers and other minor maintenance work - Inventory Manager - Adaptation to SC2.MIB - New HW: Support new BUS MIB (PCI bus segmentation) - Displaying logical partitions alongside of physical ones for Cassiopeia systems V6.30: - Scheduled suppressing of Events in Alarm-Mangment - New default for change connectivity trap - Support for SQL server 2012 - RAID informations from ESXi systems - Password expiration message - URL for iRMC in server list improved - Java 7 mandatory - Support for RHEL 6.5 - Stop Support for SLES10 - Support for Citrix Xenserver 6.2 V6.21: - New feature: support of Active Directory Groups in SVOM - New OS: Windows vNext (2012 R2) - New feature: SNMPv2c support in SVOM - Support for RHEL5 update 10 V6.20: - Support for email using MAPI is removed! Only SMTP is continued. - Backup directory server configurable - Support for SLES11 with SP3 - Support for RHEL6 update 4 - Linux: Improved shutdown duration - Show group membership in server list - Improvement for Cluster in a Box - GUI for server list settings for handling of virtual systems - Support for new hardware - Miscellaneous change requests Please regard: Due to security reasons, the username for SVOM login is restricted in the manner that the following characters are not allowed: ! # $ ' ( ) ^ ~ ` | @ * [ ] { } < > V6.12: - Support for iBBU V6.11: - Support of new OS Windows Server 2012 - Linux OS: RHEL 5.9 - Reduction of the number of static ports used by JBOSS - IPV6 only environment V6.10: - New prerequisite: JBoss Application Server 7. The setup is included in serverview.exe - Java runtime 7 support - Search function in server list - Support for ETERNUS CS800 - Attention: Upgrade possible only from V6.00.06 or higher! - V6.00: - VMWare status icons for VM's without SV agents - Import/Export servers and groups - Filtered tables in Serverlist and Alarm Monitor - IPV6 support for iRMC administrative URL's - Templates for Event Manager rules - Use LocalService account for JBoss service - Miscellaneous If systems running WMware ESXi 5 are being monitored by ServerView, it is highly recommended to install VMware ESXi 5.0 Update 1 V5.51: - CX400 support - V5.50: - GUI for OpenDS user configuration - Support for iRMC with IPV6 - Audit logging: Sign in_out events - BMC address in import/export server list - Enhancements for VIOM support - Phase out of MSDE 2000/SQL Server 2000 - Watchdog for SV services on Linux - Miscellaneous V5.30: - High Availability enhancements in serverlist service - CIM indications from ESXi - Encrypted password storage in xml files - SVOM Status Gadget - Browser support for IE9 and Firefox 4 - StorMan 4.0 and new ETERNUS models (ETERNUS DX S2 family) - Miscellaneous 3.2. Obsolete Functions The following functions are removed in this version: Alarm forwarding to MAPI destinations The following functions are supported for the last time in this version: ./. 3.3. Incompatibilities with other Delivery Units Performance Monitoring and Threshold Management are disabled by default. This also happens for an upgrade installation. To enable it again please use the settings tab in Threshold Manager or Base Configuration Wizard. 3.4. Upgrade Supported update paths: SVOM 7.01.03 -> SVOM 7.11.12 -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 7.02.02 -> SVOM 7.11.12 -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 7.10.10 -> SVOM 7.11.12 -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 7.11.12 -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 7.20.10 -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 8.xx.xx -> SVOM 8.50.02 -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 SVOM 9.xx.xx -> SVOM 9.80.02 -> SVOM 10.30.00. (Windows only) SVOM 9.xx.xx -> SVOM 9.02.02 -> SVOM 9.80.02 -> SVOM 10.30.00 (Linux only) If other ServerView products like Installation Manager are installed after Operations Manager, they have to be uninstalled before uninstalling Operations Manager. 4. Products Installation and Configuration When installing the product, you must follow the information concerning installation in the product documentation as well as the information in this Release Note. 4.1. Installation 4.1.1. All systems a) It is important that the correct network properties are chosen during installation: - IP address: If there are several networks please choose the address which you want to use for server management - Computer name and domain: Your system has to be reachable by tracert or traceroute with computername.dns_suffix. - Community: your management station has to offer SNMP access with this community b) The commands hostname and hostname -f must deliver valid names. The network configuration can be set up in various ways. This condition is satisfied for many configurations if the server IP is entered in (Linux) /etc/hosts or (Windows) C:\windows\System32\drivers\etc\hosts with its domain name. This requirement must be met before installation of SVOM. 4.1.2. Windows Please read on preparations for upgrade installation (section 4.1.2.4) before upgrading. It is good practice to perform a backup of the machine before starting the (un-)installation of ServerView. You can use the backup utility in Windows Server for this. 4.1.2.1. Installation Prerequisites a) SNMP Service must be enabled. 4.1.2.2. Installation Start serverview.exe from Windows Explorer. Please ensure that all active applications have been closed prior to the installation. Installation on a network location or on a compressed drive is not supported. 4.1.2.2.1. Silent installation: If the default settings shall be changed, the file silent_install.ini has to be edited. For a silent installation, call start /wait serverview.exe /s Silent installation in modus 'modify' (running the installation procedure of the already installed version again) will be aborted. Please use silent only for new or upgrade installations with a local SQL Server. In this case, a typical installation with all features is done by default for a new installation. On upgrade the installed features of the existing version are updated. In a silent upgrade installation the installation path in silent_install.ini is ignored. The existing path is used only. Please regard that the setup files have to be kept available for later modifications of the installed version. 4.1.2.3. Terminal Server/Remote Desktop Services installation mode If the Terminal Server/Remote Desktop Services role is installed, a special installation mode is required for installing Operations Manager: - Insert the PRIMERGY/PRIMEQUEST ServerView Suite DVD - Search for file "serverview.exe" and note the path to file "serverview.exe" - Install Operations Manager via command prompt window: Open a command prompt window and type: change user /install Type path name to the "serverview.exe" file in the same command prompt window and install Operations Manager. After the installation, type in the command prompt window: change user /execute 4.1.2.4. Upgrading Preparation before upgrading We recommend to our customers the following before upgrading to ServerView 10.30 or higher versions: IMPORTANT: Upgrade installation from ServerView versions older than 9.80.02 is not supported. - Back up the following directories \Fujitsu\ServerView Suite - It is good practice to perform a backup of the machine before starting the (un-)installation of ServerView. You can use the backup utility in Windows for this. - To take a note on the current user account of the Download Manager and Application Service. This is found in Control Panel / Administrative Tools / Services by selecting ServerView Download Service or ServerView ApplicationService, right clicking and selecting properties and then clicking on tab 'Logon'. - Sometimes the installation will be continued even after an error has occurred. We ask you to contact the Fujitsu Customer Helpdesk on how to handle the reported errors. See also the manual "ServerView Operations Manager, Installation under Windows". 4.1.2.4.1. Rollback to old ServerView version If a severe error occurs during the upgrade to ServerView 10.30 or higher then please contact the Fujitsu Customer Helpdesk. In the worst case it might be necessary that you perform a rollback to the old ServerView version. In this case please - Uninstall ServerView 10.30 or higher version - Reinstall the original ServerView version - Restore the backed up directories - Restore the ServerView database Faulty ServerView installations In rare situations it may happen that an incomplete or erroneous upgrade to ServerView results in to faulty ServerView installations. You recognize this by multiple ServerView entries in Control Panel / Programs and Features resp. Add or Remove Programs. Or the uninstallation fails and the ServerView entry remains. In the past Microsoft provided the Windows Installer Cleanup utility to support cleaning the registry. It resolved some installation problems, but it sometimes damaged other components installed on the computer. Because of this, the tool has been removed from the Microsoft Download Center. To get a clean machine you have to restore Windows from a backup you have created before the (un-) installation. - Only steps to free disk space are described here. They will not enable you to install ServerView again on this machine. - Stop existent ServerView services via Control Panel / Administrative Tools / Services and set 'Startup type' to 'Disabled' via context menu entry 'Properties': ServerView Download Service ServerView ApplicationService ServerView Remote Connector ServerView Services ServerView Apache Directory Server - Reboot the machine if services had to be stopped - Go to directory to folder %windir% - Delete files: ServerViewDB.ini, ARVendor.ini, ASVendor.ini, DNVendor.ini, EMVendor.ini, IVVendor.ini, PMVendor.ini, RVWVENDOR.ini, svappserv.ini, SWVendor.ini, UMVendor.ini. - Go to to ServerView installation folder: (default is :\Program Files\Fujitsu\ServerView Suite) and delete the following sub folders: tomee opends Remote Connector (if Fujitsu ServerView Agent is NOT installed) ServerView svcommon svom 4.1.2.5. Troubleshooting / Known Problems for installation on Windows - Sometimes an error on modify installation of package Fujitsu ServerView Application Server occurs: bq. "Sql script file GrantLoginJBoss.sql ended with error. ... User was possibly not added as SQL Server Login. Please search for troubleshooting notes regarding "GrantLoginJBoss.sql" ..." - The user shall click the OK button. The installation is continued. Open a command prompt window with selection of *** "Run as administrator" *** from the context menu. Switch to the directory \ServerView\ServerView Services\scripts\ServerView\Tools. Type GrantLoginJBoss.bat and press the Enter key. Type the name of the JBoss User Account. Check output and log file =SVGrantLogin_JBoss.log in the given folder. The success message is: bq. "... adding the account as valid Login for SQL Server granting access rights for ServerView database". Alternatively the user can install SQL Server Management Studio, start it with selection of "Run as administrator" from the context menu and add the installation account as a valid login, see manual "ServerView Operations Manager", "Installation under Windows", chapter "Adding a user account with SQL Server administrator rights". Then repeat the modify installation of package Fujitsu ServerView Application Server. - Sometimes an error on installation occurs during "Executing SQL Scripts" of GrantLoginJBoss.sql: [Microsoft][SQL Native Client][SQL Server]Windows NT user or group '...' not found. - Sometimes an error on modify installation of package Fujitsu ServerView Application Server occurs: The user shall click the OK button. The installation is continued. On new installation uninstall Fujitsu ServerView Operations Manager and Fujitsu ServerView Application Server afterwards. Repeat the installation with usage of the Browse button in the Tomee Service Logon Information dialog. On upgrade installation run the Modify installation on Fujitsu ServerView Application Server afterwards and set the Tomee Service Logon with usage of the Browse button. Explanation: When using a local SQL Server the user can work with SVOM without problems but the same error would appear in the next upgrade installation. When using a remote SQL Server the user CANNOT work with SVOM. This error happens when the user typed a User Name in the Tomee Service Logon Information dialog which could not be validated. The Tomee service is not started under this user, but under LocalSystem. - Database tool GrantLoginSecure.bat: Sometimes the grant of the access for the ServerViewDB database during installation fails. The user shall click the OK button. The installation is continued. Open a command prompt window with selection of "Run as administrator" from the context menu. Switch to the directory \ServerView\ServerView Services\scripts\ServerView\Tools Type GrantLoginSecure.bat and press the Enter key. You will be asked to enter the name of the windows account which shall be granted access to the ServerViewDB database. Please observe the following: Prerequisite: An SQL Server login for the account must already exist. The required format is: domain\username\ You will have to call the bat file for each account which is missing repeatedly. Check output and log file SVGrantLoginSecure.log in the given folder. In case of failure, the log file will contain an error message indicating the error reason. - Sometimes at the end of the installation the dialog "Updating System" does not come to an end if you executed Operations Manager installation without SQL Server "sysadmin" access and one of the necessary SQL Server logins is missing. Please look in the Windows Application Event Log for the following message: "Login failed for user '...'. Reason: Token-based server access validation failed with an infrastructure error. Error: 18456, Severity: 14, State: ... In this case add the missing user account in the SQL Server as SQL Server login. Then the installation should soon come to an end. 4.1.2.6. Configuration on Windows 4.1.2.6.1. Network Protocols for SQL Server Express installations By default, networking protocols are disabled for SQL Server 2014 Express installation. ServerView Operations Manager does however need the TCP/IP protocol to be enabled for database access. The protocol is enabled during the ServerView Operations Manager installation process only if SQL Server Express was installed automatically by ServerView setup. If SQL Server was not installed by ServerView Operations Manager setup, this must explicitly be done following SQL Server installation via SQL Server Configuration Manager: - Start the SQL Server Configuration Manager - Expand SQL Server Network Configuration - Click Protocols for Instancename, where is the name of your SQL Server Express instance installed - Right click TCP/IP and choose enable - Restart SQL Server service to apply the changes 4.1.3. LINUX Log in as the superuser "root" to execute the described installation tasks. Please read on preparations for upgrade installation (section 4.1.3.4) before upgrading. 4.1.3.1. Installation Prerequisites a) General Before installation there must be an "net-tools" package installed in the system. The most recent lists of prerequisites for each supported linux distribution are located in ./deps-rules folder. Officially supported distributions have automatic prerequisites installer based on these lists. Alternatively please use the package managers of the platforms to install missing packages. These are yast on SLES platforms and 'Add/Remove Software' in menu bar as well as yum on RHEL platforms. These platform managers implicitly resolve all dependencies. You may check whether a package is installed with the command rpm -q . On RHEL / 64-Bit systems you must use rpm -q --queryformat "%{NAME} %{ARCH}" in order to view the architecture of the package. Please pay attention to this. For RHEL / 64-Bit platforms we always also state the architecture of the package separated by a dot from the package name. You can directly use this syntax 'name.arch' in the package manager. b) List of Prerequisite Packages for RHEL b.1) RHEL 7.8 64-Bit libc.x86_64 gzip.x86_64 keyutils-libs.x86_64 krb5-libs.x86_64 libcom_err.x86_64 libconfig.x86_64 libcurl.x86_64 libgcc.x86_64 libselinux.x86_64 libstdc++.x86_64 libtool-ltdl.x86_64 libxml2.x86_64 ncurses-libs.x86_64 net-snmp.x86_64 nss-softokn-freebl.x86_64 openldap-clients.x86_64 openssl-libs.x86_64 pcre.x86_64 policycoreutils-python postgresql.x86_64 postgresql-odbc.x86_64 postgresql-server.x86_64 systemd-libs.x86_64 unixODBC.x86_64 unzip.x86_64 xz-libs.x86_64 zlib.x86_64 Prerequisites for special functionality: DeskView Interface: curl XEN/KVM monitoring: libvirt-client b.2) RHEL 7.9 64-bit See package list of RHEL 7.8 64-Bit. b.3) RHEL 8.4 64-bit glibc.x86_64 gzip.x86_64 keyutils-libs.x86_64 krb5-libs.x86_64 libcom_err.x86_64 libconfig.x86_64 libcurl.x86_64 libgcc.x86_64 libselinux.x86_64 libstdc++.x86_64 libtool-ltdl.x86_64 libxml2.x86_64 ncurses-libs.x86_64 net-snmp.x86_64 nss-softokn-freebl.x86_64 openldap-clients.x86_64 openssl-libs.x86_64 pcre.x86_64 policycoreutils-python-utils.noarch postgresql.x86_64 postgresql-odbc.x86_64 postgresql-server.x86_64 systemd-libs.x86_64 unixODBC.x86_64 unzip.x86_64 xz-libs.x86_64 zlib.x86_64 b.4) RHEL 8.5 64-Bit See package list of RHEL 8.4 64-Bit b.5) RHEL 8.6 64-Bit See package list of RHEL 8.4 64-Bit b.6) RHEL 8.7 64-Bit See package list of RHEL 8.4 64-Bit b.7) RHEL 8.8 64-bit See package list of RHEL 8.4 64-Bit b.8) RHEL 9 64-bit glibc.x86_64 gzip.x86_64 keyutils-libs.x86_64 krb5-libs.x86_64 libcom_err.x86_64 libconfig.x86_64 libcurl.x86_64 libgcc.x86_64 libselinux.x86_64 libstdc++.x86_64 libtool-ltdl.x86_64 libxml2.x86_64 ncurses-libs.x86_64 net-snmp.x86_64 nss-softokn-freebl.x86_64 openldap-clients.x86_64 openssl-libs.x86_64 pcre.x86_64 python3-policycoreutils.noarch postgresql-odbc.x86_64 postgresql-server.x86_64 systemd-libs.x86_64 unixODBC.x86_64 unzip.x86_64 xz-libs.x86_64 zlib.x86_64 b.9) RHEL 9.1 64-Bit See package list of RHEL 9 64-Bit b.10) RHEL 9.2 64-Bit See package list of RHEL 9 64-Bit c) List of Prerequisite Packages for SLES c.1) SLES12 SP4 64-Bit cyrus-sasl glibc gzip krb5 libcom_err2 libconfig9 libcurl4 libgcc_s1 libidn11 libkeyutils1 libldap-2_4-2 libltdl7 libstdc++6 libsystemd0 libxml2-2 libz1 net-snmp openldap2-client postgresql94 postgresql94-server termcap unixODBC unzip Prerequisites for special functionality: DeskView Interface: curl XEN/KVM monitoring: libvirt c.2) SLES12 SP5 64-Bit See package list of SLES12 SP4 64-Bit. c.3) SLES15 SP2 64-Bit cyrus-sasl glibc gzip krb5 libcom_err2 libconfig11 libcurl4 libgcc_s1 libkeyutils1 libldap-2_4-2 libstdc++6 libxml2-2 libz1 net-snmp openldap2-client postgresql12 postgresql12-server unixODBC unzip Prerequisites for special functionality: DeskView Interface: curl XEN/KVM monitoring: libvirt c.4) SLES15 SP3 64-Bit See package list of SLES15 SP2 64-Bit. c.5) SLES15 SP4 64-Bit cyrus-sasl glibc gzip krb5 libcom_err2 libconfig11 libcurl4 libgcc_s1 libkeyutils1 libldap-2_4-2 libopenssl3 libstdc++6 libxml2-2 libz1 net-snmp openldap2-client postgresql12 postgresql12-server unixODBC unzip Prerequisites for special functionality: DeskView Interface: curl XEN/KVM monitoring: libvirt c.6) SLES15 SP5 64-Bit See package list of SLES15 SP4 64-Bit. Further Prerequisites d.1) Network Configuration It is necessary that the IP address 127.0.0.1 for localhost is contained in /etc/hosts. This is needed for the access to the PostgreSQL server. The command hostname and hostname -f must provide correct names. Network configuration is done in different ways. Often problems can be solved by adding the result of 'hostname' and 'hostname -f' and the corresponding IP address to /etc/hosts. The IP address for both should naturally be the same. If not then there is already something strange in your network configuration. At installation time the name of the server during silent installation is determined in the following way: hostname -f, hostname, localhost. So if hostname -f fails, then hostname is tried, if this fails the name of the computer is set to localhost. During interactive installation the same method is used to provide the suggested server name that you may correct to your needs. Under rare network configurations it may happen that ServerView Operations Manager can operate correctly only with either the name of 'hostname -f' or 'hostname' when accessed from some specific management console. In such a case try reconfiguring ServerView Operations Manager to use the other name. You may do so by calling command /opt/fujitsu/ServerViewSuite/svom/ServerView/Tools/ChangeComputerDetails.sh. For monitoring you always need to check whether the server name of the central management station can be resolved at the management console. Simply perform a ping on the management console. If the central management station cannot be reached you need to investigate your network. d.2) SELinux Please note that if SELinux was disabled during SVOM installation and has been enabled after SVOM installation you may have to take actions (manual SELinux polices definitions) to allow e.g. access for virsh, snmptrapd. d.3) super user access During installation the user 'postgpls' is created, and needs super access during installation and during operation of ServerView OM. The user 'postgpls' is locked so that it can only be used via su. Please leverage superuser access restrictions before starting installation. You may reset them afterwards, but need to allow superuser access for 'postgpls'. d.4) Access rights The directory /tmp must have write, read, execute access for all(world). The database server is running under account postgpls, and needs to create named pipe and lock file in directory /tmp. d) Prerequisite package from the distribution Install Mozilla/Firefox. e) Configuring yum You need to provide a configuration file in /etc/yum.repos.d to make the DVD or the iso-file of the RHEL distribution known to yum. Step 1: Often the RHEL distribution DVD or an iso-file of the DVD is mounted to the directory: /media/RHEL xxx xxx xx, containing several blanks. Yum cannot handle such paths. Therefore do the following: ln -s '/media/RHEL xxx xxx xx' /tmp/instmedia Example: ln -s '/media/RHEL-7.8-x86_64-dvd1.iso' /tmp/instmedia Note: the automatic typing extension of the shell might insert \ before the blanks into the path name of the RHEL iso. Be sure to remove them. Step 2: The RHEL DVD / iso file contains several yum repositories. You need to specify each of the repositories in the yum configuration file, if you want to use it. In directory /etc/yum.repos.d create a file named rhel_dvd.repo with the following contents: Example for RHEL7: [dvd] name=RHEL 7.8 iso image baseurl=\'file:/tmp/instmedia/\' enabled=1 epgcheck=0 Example for RHEL8: [rhel-dvd-server] name=Red Hat Enterprise Linux - DVD Server Repository baseurl=file:///tmp/instmedia/BaseOS enabled=1 gpgkey=file:///tmp/instmedia/RPM-GPG-KEY-redhat-release gpgcheck=0 [appstream] name=Red Hat Enterprise Linux - DVD Server Repository II baseurl=file:///tmp/instmedia/AppStream enabled=1 gpgkey=file:///tmp/instmedia/RPM-GPG-KEY-redhat-release gpgcheck=0 Step 3: Test your configuration of yum: yum list unixODBC should list - unixODBC.x86_64 on RHEL / 64-Bit - unixODBC on SLES / 64-Bit 4.1.3.2. Installation Upgrade is only possible from ServerView 9.80.02 or later versions and may only be done via script install.sh Please see also section 'Preparation before upgrading on Linux' below. The syntax is: /bin/bash install.sh [-OM ] [-EM [-UM]] [ -q|--quiet] [-f|--force] [-v|--verbose|--debug] [--snmp-community] [--ipaddr] [--ipchangecheck] [-i|--installdir] [-l | --lang] [-d|--ds-dialog] -OM Operations Manager only, that is without EventManager -q|quiet silent installation -v|--verbose|--debug debug mode activated -f|--force force installation without error checks --snmp-community specify the snmp community to which the central management station belongs (necessary if other than community public) --ipaddr By default the first IP address found is used as local IP address for the central management station. If several IP addresses are available for the central management station you may specify another one. Only a valid IP address is accepted. --ipchangecheck [yes|no] By default the ServerListService checks whether the IP address of the central management station has changed. This behaviour may be turned off by specifying no. You must specify this value if you specified an IP address different from the default IP address. -i|--installdir specify the directory in which the packages are located. Example: /SVSSoftware/RPMS -l|--lang specify the language in which SVOM GUI is displayed. Possible values are en or ja for English / Japanese. If the language is not specified and option -q is not given, then you will be asked the language. For quiet installation this parameter MUST be specified. --chgtrap [yes|no] Change settings for 'connectivity changed notification' during an upgrade installation. Choose yes to change it for all servers to 'enabled'. -d|--ds-dialog display dialog to allow specification of parameters for alternative directory service When the complete Operations Manager is to be installed, it is sufficient to execute install.sh. Parameters for the alternative directory service can be specified completely as command line arguments. Please see the manual or type install.sh -? to receive information. Note 1: A log of the installation is created in /var/log/fujitsu/ServerViewSuite/ServerView/install.log. Note 2: The database server PostgreSQL will be automatically installed. The ServerView database is preserved. In case of an upgrade, user specific changes in files postgresql.conf, pg_hba.conf, pg_ident.conf are lost. Please reenter them. The previous configuration files are saved in /etc/fujitsu/ServerViewSuite/Postgresql. Note 3: the following packages will be installed: If the complete Operations Manager is installed the following RPM packages are installed: ServerView Operations Manager references all packages of Operations Manager ServerViewBase provides configuration of Operations Manager and the ServerView specific WebServer instance ServerViewConnectorService provides the remote connector service ServerViewDB provides the ServerView database ServerViewTomee provides the Tomee server ServerViewCommon Provides files needed by both Operations Manager and EventManager ServerViewEventManager (*) provides the EventManager ServerView_S2 (\*) provides the Operations Manager (without EventManager) ServerViewUpdateManager provides the UpdateManager *...... either ServerViewEventManager or ServerView_S2 must be installed Note 4: the user 'postgpls' is created by ServerViewDB. It is equivalent to the user 'postgres' in the PostgreSQL documentation. The user 'svuser' and the group 'svgroup' are created by ServerViewBase. Most of the programs of ServerView Operations Manager are started under this group. Note 5: the following message is displayed, if package libvirt or libvirt-client is missing. WARNING: Package is missing. Therefore you cannot monitor virtual machines running in RHEL6/KVM. You may install the package anytime when you need this functionallity. Note 6: If you uninstall ServerView and restart a new installation, it may happen that a message like "ERROR: Port 9212 is used by , see 'netstat --antp'." is displayed. This situation should be gone after a little while and new installation should be possible. This is caused by some time delay until ports are released for reuse. Note 7: During installation you have to specify password for accessing directory service. Password may also contain blanks or special characters. These characters must be preceded by a backslash. Desired Password: " 123 qwe " Necessary Input: "\ 123\ qwe\ " 4.1.3.3. Adaptation of configuration parameters Configuration parameters are stored in file /etc/fujitsu/ServerViewSuite/ServerView/global.conf. Adaptation should be hardly ever necessary, and should only done with appropriate consideration. You may specify many parameters when using the installation script install.sh. E.g. the parameter --snmp-community allows to specify a community other than public. If you want to change parameters after installation, proceed as follows: a) For changing the directory service, specifying parameters for Microsoft Active Directory Service, the fully-qualified hostname or the IP address use the script ChangeComputerDetails.sh. It is located in directory /opt/fujitsu/ServerViewSuite/svom/ServerView/Tools. b) For changing the snmp community or the behaviour for checking the IP address, proceed in the following way after installation of ServerView Operations Manager: - stop all ServerView services with: /usr/bin/sv_services stop - edit file /etc/fujitsu/ServerViewSuite/ServerView/global.conf - execute /usr/bin/configure-ServerView.sh - If you changed parameter COM_IPCHANGECHECK then call additionally: - - run: PACKAGE=ServerViewCommon; /usr/bin/configure-Server.sh Note that both statements must be on one line. - If you changed parameter COM_SNMP_COMMUNITY call additionally: /opt/fujitsu/ServerViewSuite/ServerView/scripts/install/ServerViewCommon/SVDBClient.sh - restart all ServerView services with /usr/bin/sv\services start 4.1.3.4. Effects of ServerView Operations Manager on system files on Linux ServerView Operations Manager requires a database to be available on the central management station. For Linux systems, PostgreSQL is used. This database requires a local database account in order to add new tables. Therefore, a new user 'postgpls' is added to the system during installation. Adding a new user to a Linux system modifies the following files (this is done via standard Linux tools): /etc/passwd add user 'postgpls' e.g.: "postgpls:x:103:100::/opt/fujitsu/ServerViewSuite/Postgresql/pgsql:/bin/bash" add user 'svuser' /etc/shadow add password for user 'postgpls' /etc/mailcap (side effect of new user; not on all OS) /etc/group add group 'svgroup' on RHEL group postgpls is implicitely created. To enable ServerView to access the PostgreSQL database, entries have to be added into the following ODBC configuration files: - /etc/[unixODBC]/odbc.ini add postgres database information for ServerView - /etc/[unixODBC]/odbcinst.ini add postgres driver information for ServerView Finally, PostgreSQL requires periodic jobs to backup and cleanup the database. This makes sure that temporary database files will not grow indefinitely. Periodic tasks are started by adding files to /etc/cron.d without modifying system files. Note that ServerView creates cron jobs by adding the file pg_CrontabEntry into the directory /etc/cron.d. For snmptrapd the configuration file /etc/snmp/snmptrapd.conf is changed to contain the entries disableAuthorization yes ignoreAuthFailure yes 4.2. Configuration on Linux and Windows 4.2.1. User management New from version 5 on is a role based user concept. Access to ServerView is controlled by privileges defined by roles. Therefore, you have to login first. The users can be derived from an existing directory service or from local directory server installed with ServerView. If local directory server is chosen during installation, the following users are available. User Password Role Administrator admin Administrator Operator admin Operator Monitor admin Monitor UserManager admin UserAdministrator You should change the default passwords after installation. For more details see the "User management in ServerView" manual. To check the connection to the chosen directory service, test scripts are generated during installation: Windows: Click "Test" in directory server configuration dialog during installation Linux: /opt/fujitsu/ServerViewSuite/tomee/svconf/CheckDS.sh Script can be called without arguments. 4.2.2. JMX port JMX port is no longer fixed and can now be changed as required. Default port is 19876, the port can be changed by modifying JMX_PORT variable assignment in file: Windows: \tomee\bin\setenv.bat Linux: /opt/fujitsu/ServerViewSuite/tomee/setenv.sh for Linux After changing this file restart is required (restarting TomeeEE is sufficient). 4.3. Uninstall 4.3.1. Windows You uninstall the Operations Manager software via the Windows' Control Panel -- Programs and Features window. First you must uninstall Fujitsu Software ServerView Operations Manager and then Fujitsu Software ServerView Application Server. 4.3.2. Linux By default, the complete Operations Manager software including the database management system is uninstalled. UninstallServerView.sh Syntax: /usr/bin/UninstallServerView.sh [-OM] [-v | --verbose | --debug] [-q] [-f|--force] -OM Only Operations Manager is uninstalled. An installed Update Manager is also uninstalled. -v | --verbose | --debug Writes additional information to the log file -q|quiet silent uninstallation -f|--force force uninstallation without error checks Note 1: A log of the uninstallation is created in /var/log/fujitsu/ServerViewSuite/ServerView/uninstall.log. Note 2: If managed servers are already added to the server list, and then ServerView\S2 is uninstalled (option --OM). The server list is not cleared. All servers will remain visible in Event Manager. 5. Product Start-Up 5.1. Windows 5.1.3. Start problem with file C:\Program If a file named like C:\Program exists on your management station in the windows partition, ServerView will not be able to start properly. When your system reboots, Windows detects this file, warns you and asks you to rename it. Please change the file name at this time, or rename it prior to starting ServerView. 5.1.4. Configuration of SNMP service In SNMP security configuration you specify, from which community and server you want to accept packets. (On the machine, where the ServerView application runs). When configuring the SNMP-Service of a Windows Server (Server with SNMP Agents) you are asked for the trap destination. Here you should enter the IP-Address of your console as well. The Server with the SNMP agents also needs to accept SNMP requests from its own IP address and from the local IP address ("127.0.0.1" or "localhost") 5.1.5. Changes of Computer Name, Domain/Workgroup membership, IP Address or Tomee service account If the computer name, the membership in a domain/workgroup, the IP address of the system, the directory service or the Tomee service account is changed after the installation of ServerView Operations Manager, the ServerView application will not work correctly. In this case run the ServerView Application Server setup again and choose option 'Modify'. The Modify installation is described in-depth in the manual "ServerView Operations Manager, Installation under Windows". 5.1.6. Adding server to empty list after system restart If, after system is restarted with empty server list, newly added servers stay in the "Explore" state (nor successive "Explore All" does work), the solution is to restart "ServerList Services" service in Services system window. 5.2. Linux 5.2.1. Keyboard Navigation with Linux Mozilla browser On Linux the keyboard navigation with Linux Mozilla browser doesn't work correctly. 5.2.2. Event Manager / Receipt of traps In order to receive traps, the following must be done for SLES and RHEL: Edit (or create if not exists) a file: /etc/snmp/snmptrapd.conf Add/edit the line disableAuthorization yes 5.2.3. Configuration of libvirtd On a KVM server the demon libvirtd has to be configured in /etc/libvirt/libvirtd.conf: max_clients = 600 max_workers = 600 max_requests = 600 A restart of the demon is necessary afterwards. 6. Hints 6.1. Common 6.1.4. Unified RBAC 6.1.4.1. User with role being member of a group with role If a user has been given a specific role and is assigned to an AD group with the same role, then it may not be possible for them to log into SVOM. In this case the solution is to remove specific role from user (the role remains assigned to the group). 6.1.5. Security 6.1.5.1. Updated SSL/TLS configuration of Application Server Configuration of SSL/TLS has been amended in order to facilitate protection against SSL attacks. Cipher suites and SSL protocols used by ServerView Application Server can be configured during ServerView Operations Manager installation. There are three defined configuration sets available: - Modern: TLSv1.3 - Intermediate: TLSv1.2, TLSv1.3 (default) - Old: TLSv1.0, TLSv1.1, TLSv1.2, TLSv1.3 The configuration of the cipher suites and SSL protocols is stored in the \tomee\conf\server.xml configuration file. 6.1.5.2. Disabling new security features in SVOM. a. Change following files: ads-transportid=ldaps.ldif File path: Windows \apacheds\instances\default\conf\ou=config\ads-directoryserviceid=default\ou=servers\ads-serverid=ldapserver\ou=transports\ads-transportid=ldaps.ldif As a default, will be specified C:\Program Files (x86)\Fujitsu\ServerView Suite\. Linux /opt/fujitsu/ServerViewSuite/apacheds/instances/default/conf/ou=config/ads-directoryserviceid=default/ou=servers/ads-serverid=ldapserver/ou=transports/ads-transportid=ldaps.ldif Changes: Comment out (by adding '#') at the beginning of following lines; ads-enabledCiphers: TLS_AES_128_GCM_SHA256 ads-enabledCiphers: TLS_AES_256_GCM_SHA384 ads-enabledCiphers: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ads-enabledCiphers: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ads-enabledCiphers: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ads-enabledCiphers: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ads-enabledCiphers: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 ads-enabledCiphers: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 ads-enabledProtocols: TLSv1.3 ads-enabledProtocols: TLSv1.2 Example: # ads-enabledProtocols: TLSv1.2 server.xml: File path: [Windows] \tomee\conf\server.xml As a default, will be specified: C:\Program Files (x86)\Fujitsu\ServerView Suite\. [Linux] /opt/fujitsu/ServerViewSuite/tomee/conf/server.xml Changes: a. Remove following attributes from "Connector" tag which includes "ssl" tag whose name attribute is "https"; protocol="TLSv1" cipher-suite=\... b. Restart SVOM services Windows Stop: - ServerView Download Service - ServerView Services - ServerView ApplicationService - ServerView Apache Directory Server Start: - ServerView Apache Directory Server, - ServerView ApplicationService, - ServerView Services, - ServerView Download Service Linux Stop /usr/bin/sv_services stop -withTomee -withPostgres Start /usr/bin/sv_services start -withTomee -withPostgres 6.1.6. SNMP 6.1.6.1. Unsuccessful browsing with SNMPv3 enabled When trying to browse for servers with SNMPv3 enabled on CMS, with only a few (SNMPv3-enabled) servers in subnet, browsing may timeout. It is recommended to add SNMPv3 hosts to sever list individually. If automated browsing in this hosts configuration is required, the following steps should be performed: - Disable SNMPv3 on CMS - Make sure SNMPv3 hosts also communicate in SNMPv1 - Browse the subnet - Add all required servers to server list - Enable SNMPv3 on CMS - Disable SNMPv1 on servers if required. 6.1.6.2. User's credentials for SNMPv3 This is required that all the nodes operating with SNMPv3 have defined the same SNMPv3 user and password. The requirement is a result of single credentials storage available in SVOM. 6.1.6.3. CMS visibility in SVOM In order to allow CMS to be visible by itself in the SVOM it required to properly configure SNMP service on the CMS. Windows: Go to 'Services', in the properties of SNMP service go to 'security' tab and click the "add" button under "accepted community names" to insert "public". Linux: In the snmpd.conf file user must add following line: 'rwcommunity public default' ". After these changes are done it is necessary to restart SNMP service. 6.1.6.4. Notes on changing global configuration of SNMP on Linux File /etc/snmp/snmp.conf contains common configuration for all net-snmp tools including snmptrapd used by SVOM. Changing this file, especially within mibs directive (concerning translation of oids to human-readable form) affects trap functionality of SVOM. If such problems occur, consider reverting to default net-snmp configuration. 6.1.7. Browsers 6.1.7.1. Proxy server problem If a ServerView start window is unreachable in your browser: Either switch off the use of a proxy server in the browser settings or add CMS's IP-Address and/or the name of the CMS server to the Exceptions list. 6.1.8. Language support 6.1.8.1. ServerView Operations Manager and ServerView Agent compatibility in scope of non-English languages support Due to change of text data encoding in SVAgent V9.50.02 some new limitations have arisen in SVOM and SVAgent compatibility. For correct display of all non-latin characters, SVAgent version 9.50.02 (or newer) and SVOM 9.70.00 (or newer) are required. If SVOM 9.70.00 is used with SVAgent older than 9.50.02, there could be some undecoded symbols instead of non-latin characters. Usage of SVAgent version 9.50.02 or newer with SVOM older than 9.70.00 is not recommended as it most likely will cause application crash in 'Single System View' and 'Archive Manager -- View archive' sub-views. Furthermore, due to encoding change, viewing archives in SVOM 9.70.00 will not be stable for archives created for systems with SVAgent older than 9.50.02. Same applies for SVOM older than 9.70.00 and SVAgents newer than 9.50.02. 6.1.9. System-related 6.1.9.1. Removal of trace files (Windows) Access to the SQL database is logged by default in trace files located in /scripts/ServerView/common/SVDBTrace*.log. By default trace files are deleted on restart of ServerView services. You change this behavior by editing the file ServerViewDB.ini in the Windows directory and setting the parameter KeepTraceFiles to 1 and thus keeping trace files for diagnosis. Please be careful not to corrupt this file. Please stop ServerView services before this adaptation and start them afterwards. Restarting services can be accomplished via the Windows services GUI. 6.1.10. SVDBServer process In some situations, the process SVDBServer cannot connect to the database because more retry time would be necessary. The retry time can be configured in the file SVDBServer.ini: startupWaitingPeriod Default is 120 seconds, it should be set to 240. 6.1.11. Configuration of libvirtd for XEN and KVM On a KVM server the demon libvirtd has to be configured in /etc/libvirt/libvirtd.conf: max_clients = 600 max_workers = 600 max_requests = 600 SVOM uses following ports for XEN and KVM connection and libvirtd.conf should be configured with following values: XEN KVM ---- TCP 16510 16509 TLS 16515 16514 A restart of the demon is necessary afterwards. 6.1.12. SELinux/AppArmor SVOM requires to run external programs from Linux distribution, e.g. virsh or net-snmp executables. What's more, user can define own applications to be run on events received by SVOM. Therefore, when using application execution protection systems like SELinux/AppArmor, this functionalities of SVOM may become unusable. This is thus recommended to run SELinux/AppArmor in the monitoring (i.e. permissive/complain) mode first. Execution prohibiting (i.e. enforced) mode may be enabled after applying required custom access control rules. 6.2. ServerView Event Manager 6.2.1. Broadcast Forwarding Forwarding to broadcast may fail sometimes due to problems of the used Windows messenger service. You can test it with the command 'msg'. This command cannot send to domains. Message length is restricted to 255 characters. To test the availability, open a CMD command box and try the following: msg for testing broadcast to specific user or msg * for testing a broadcast to all users on the current server. If one of these commands does not work, you have to correct the network problem first. 6.2.2. Event Log Forwarding If the Event Manager runs on the same machine as the ServerView agents, be careful with logging alarms into the NT event log. In the case, that the ServerView agents are configured to send a trap on event log changes, a loop can occur. This means, Event Manager writes the alarm into event log, the agents generate a trap, Event Manager writes to event log .... and so on. To avoid this loop, don't store alarms in event log (neither in overall settings nor for the special event log traps from the ServerView agents), if the event log traps are enabled in the agents. Those event log traps are: Event log entry: error Event log entry: warning Event log entry: information If you do not enable such traps in ServerView, if Event Manager is running on the same system as the agents, the loop cannot occur. 6.2.3. Forwarding traps to management stations Depending on your system configuration, it may cause problems, if you put too many station's forward entries into one alarm group. In this case not all stations will get the forwarded trap. If this happens, just reduce the number of station entries in the alarm group. 6.2.4. SMTP Mail forwarding 6.2.4.1. Supported SMTP Authentication methods Following SMTP Authentication methods are supported: CRAM-MD5 LOGIN PLAIN 6.2.4.2. SMTP Mail Forwarding in Linux If you do not have DNS configured in your network or there are problems translating the SMTP server name into its IP Address, edit the file '/etc/hosts' and add the SMTP servers IP Address and Computer Name. If the problem persists, you must define the IP Address of your 'SMTP server' in the corresponding field of the Event Manager 'Mail Properties (SMTP)' dialog. 6.2.5. Servers send trap "Unauthorized message received" There can be three different reasons for that: a) The server's SNMP configuration does not accept SNMP packages from the ServerView console b) The server's SNMP configuration does not allow SNMP operations for the community, which is configured in the console's server list. c) Another SNMP based application in your network tries to use SNMP for the server and has the wrong community or is not allowed to do that (reason 1). 6.2.6. Forwarding to executable on Windows Due to the new service hardening concept in Windows, no interactive applications can be called via alarm forwarding (destination type 'executable'). Such applications are started, but display no GUI and hang in background. 6.3. ServerView RAID 6.3.1. Security Settings in Internet Explorer 11 Some security settings may cause problems with opening the web page of ServerView RAID. In this case please add the site of ServerView RAID to the trusted sites zone. 6.4. Networking 6.4.1. Network Notes Getting values over the network may not always work properly. The effects and the reasons for that are manifold: - Some network information is sometimes not detected when the Microsoft Windows Network is browsed. This behavior is due to the method that MS-Windows uses to get the network information (i.e., by broadcast methods). - Only computers that are running are found. - For SNMP access, the server, where ServerView Operations Manager is running, must be configured in the SNMP-Properties of the monitored server (community, accessibility). - Before you add a new server, you should test its connectivity. To do that, fill the NetAddress or ServerName field in the ServerBrowser Address Dialog and click on the Test button. If the NetAddress or the Servername could not be resolved, please manually enter the Servername and the NetAddress. - If a server becomes unknown although the IP address is known, that computer is not running, or you have a network problem. - The computer name to IP address resolution may be slow; you may have not set up the Windows Internet Name Services (WINS) or the Domain Name System (DNS) correctly on your login computer. The addresses of the primary or secondary WINS servers or the addresses of the DNS servers may not be valid. If the WINS protocol has not been properly activated, the IP address resolution uses name query broadcasts which are pretty slow. You can set up the WINS and DNS in the TCP/IP properties of the network settings. Mapping Computer Names to IP Addresses and vice versa Computer names are resolved to IP addresses using any combination of WINS, name query broadcasts, the LMHOSTS file and DNS. We recommend that you implement WINS for name resolution and browsing support. If an IP address could not be found, this could be caused by several reasons: - TCP/IP is not installed on the remote computer. - No WINS server or any other information source - LMHOSTS file, DNS has not been established in your LAN. - WINS is not enabled on your login computer. - The database of the WINS is not up-to-date. - If the address could not be resolved by the WINS, DNS or any LMHOSTS file, a name query broadcast is used. This broadcast may fail due to the network topology or performance problems. For instance, if domains are separated by routers, special problems can arise because broadcasts, by default, do not pass through routers. Note: These Network Notes concern the computer where the ServerView Operations Manager is installed and running; but not necessarily, where www-browser used to open SVOM is running! 6.4.2. Tomee and rarely used ports Port 1473: This is the non-SSL port of ServerView's directory service (ApacheDS) for LDAP queries. Normally it should not be used for security reasons in favor of port 1474, which is the SSL LDAP port. This means that a customer may safely lock the port by the firewall, except he/she intentionally wants to use it. Port 8000: This is Tomee port for remote debugging. It is left configured in the shipped product because it is useful from time to time for diagnostic purposes, however it is inactive by default. 6.5. Database Server and Database Related Notes 6.5.1. Windows 6.5.1.1. Database backups - Shrinking logs on Windows The database backup is documented in detail in the manual "ServerView Operations Manager, Installation under Windows". If you selected advanced backup mode during installation (default was typical), you should check from time to time whether the backup jobs JobServerViewHourly and JobServerViewLongInterval are being executed, to prevent the log file ServerViewDB_log.LDF from getting too big. Else file ServerViewDB_log.LDF grows to a size of several gigabytes and disk space runs short. To shrink the file, please follow the instructions in: \ServerView Services\scripts\ServerView\Tools\Shrink_ServerViewDB_log.LDF.doc Please check why the database backup jobs do not run. 6.5.1.2. Setting SQL Server memory option on Windows ServerView Operations Manager offers a Windows utility tool (.bat file) to set the max server memory option in the Microsoft SQL Server instance that Operations Manager uses according to customer input (see chapter "Setting SQL Server memory option" in the Windows installation manual). The tool may be used as follows: -Open a command prompt window. -Find out and switch to the directory: type %windir%\ServerViewDB.ini | findstr -i DllPath= cd /d \Tools -Execute the tool: SVConfigSQLMaxMemSize.bat 6.5.2. Linux 6.5.2.1. Reuse of dumps on Linux Dumps which are created on one server, may not be reusable on another server. This may happen when the upgrade history of SVOM on the two servers differ. 6.5.2.2. Handling of large database server log on Linux The PostgreSQL server is configured to rotate its log files. These are located in /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data/pg_log. If you do not need older log files, you may remove them. 6.5.2.3. Changing from Local Database Server to Remote Database Server and vice versa on Linux a) Changing from local to remote: Install remote database server as described in manual. On central management station execute as root: /opt/fujitsu/ServerViewSuite/ServerView/scripts/change-DB.sh --remote b) Changing from remote to local: On central management station execute as root: /opt/fujitsu/ServerViewSuite/ServerView/scripts/change-DB.sh --local Uninstall remote database server as described in manual. Note: customer specific changes in the database server configuration files cannot be transferred automatically to the new active database server. Any customer specific configuration needs to be done manually, by editing the configuration files of the active database server. This refers to the files postgresql.conf, pg_hba.conf and pg_ident.conf. 6.5.2.4. Database user for PostgreSQL The database user svuser is created for the ServerView Operations Manager. All access to the database are made by this user. So when using any commands like psql, pg_dump this user must be specified. For example for accessing the database via psql, you need to specify the parameters psql [-h IP-Address] -p 9212 -U svuser -d ServerViewDB The parameter -h is only needed in case of a remote database. 6.5.2.5. Crash of database server 'postgresql' If ServerView continuously produces very strange results, please check whether the postgresql has crashed. Usually there would be a message in /var/log/messages saying that the postgresql has been killed. Use 'systemctl status sv-postgresql.service' to check process status. You may as well execute 'ps ax | grep postgresql' in a shell window and see whether a postgresql process is reported. Before restarting the postgresql please stop all ServerView services and after restart of the postgresql also restart the ServerView services. This is done by executing the following commands: /usr/bin/sv_services stop -withPostgres /usr/bin/sv_services start -withPostgres 6.5.3. Remote SQL Server/PostgreSQL If the option remote database is used, forwarding to executable with GUI (see above) is also not possible, as the ServerView service has to run with the domain user account and therefore can have no interaction with the desktop (Windows only). If connection to remote database gets lost when Server View Operation Event Manager is running (e.g. when SQL Server machine is rebooted or remote database service stopped/restarted), ServerView Services have to be restarted manually. 6.6. VME 6.6.1. General notes VME (Virtual Management Extension) supports the following host versions: - VMware ESX (>= 3.5) - VMware 3i (>= 3.5) - Microsoft Hyper-V - Xen (>= 3.1) - XenSource (>= 3.1) on the level of Xen - CitrixXen - KVM If systems running WMware ESXi 5 are being monitored by ServerView, it is highly recommended to install VMware ESXi 5.0 Update 1 6.6.2. CIM provider version visibility When user upgrades CIM agent, the updated CIM agentĀ“s version will be visible in the Single System View once the server is restarted 6.7. Threshold Manager Predefined Thresholds may not be adequate for your specific server configuration. If you receive too many 'threshold exceeded' traps, it is recommended to adopt the default threshold templates using Threshold Manager. 6.8. User Management 6.8.1. Role assignment Please note that with current version of the Operations Manager UI only role assignments to users are supported. Assignments to groups can not be done via Operations Manager UI. 6.8.2. Backup and Restore of ApacheDS User Configuration If the user configuration in ApacheDS is changed backup and restore can be done in the following way: Important: Restore has to be done to the same or newer version of Operations Manager as backup was taken! For Windows: Backup: - Open command prompt window - Type and execute in order: cd ServerView Suiteapachedsbin ldapsearch.exe -H "ldap://localhost:1473" -D "uid=admin,ou=system" \ -y "" -s sub -b "dc=fujitsu,dc=com" > "apacheds-export.ldif" Restore: - Stop Service 'ServerView ApplicationService' - Open command prompt window - Type and execute in order: cd ServerView Suite apachedsbin ldapmodify.exe -H "ldap://localhost:1473" -D "uid=admin,ou=system" \ -y "" -a -c -f "apacheds-export.ldif" 4. Start Service 'ServerView ApplicationService' For Linux: - Backup: - Open shell window - Type and execute: cd /opt/fujitsu/ServerViewSuite/apacheds/bin su svuser ldapsearch -H "ldap://localhost:1473" -D "uid=admin,ou=system" -y \ "" -s sub -b "dc=fujitsu,dc=com" > "apacheds-export.ldif" exit - Restore: - Open shell window - Type and execute in order: systemctl stop sv-tomee cd /opt/fujitsu/ServerViewSuite/apacheds/bin su svuser ldapmodify -H "ldap://localhost:1473" -D "uid=admin,ou=system" -y \ "" -a -c -f "apacheds-export.ldif" systemctl start sv_tomee 6.8.3. Changing group type in Active Directory from Distribution to Security The necessary script was created and put under the path SrvView_Common\JavaEE\Tomee\Setup\. The script works only when the Execution Policy is set to Unrestricted. It's possible to check what's the current value of Execution Policy by running a PowerShell command: Get-ExecutionPolicy If the value is different from Unrestricted then the Domain Administrator should use the following PowerShell command to change it: Set-ExecutionPolicy --ExecutionPolicy Unrestricted Later on, while running the script, user should provide a name of the role that will have the group type changed from Distribution to Security. The usage of the script is as follows: .\grouptype.ps1 --role <> e.g. .\grouptype.ps1 --role Administrator After that the group type for the mentioned role will have the new value assigned (Security). 6.9. ServerView Download Service After a silent installation, the user account for the ServerView Download Service is set to local system account and can be changed manually. For details please see the manual "ServerView Update Management, User Guide", chapter "Prerequisites on Central Management Station (CMS)". 6.10. Update Management (including Download Manager) ServerView Update Manager (SVUM) is an additional feature of ServerView Operations Manager (SVOM), and consists of the following applications: - Update Manager - Repository Manager - Download Manager - Configuration a) Hints on Error situations see Online Help/Manual of ServerView Update Manager > Troubleshooting. b) Hint concerning Blade Server and virtual systems: Server Blades or guest systems might be deleted from ServerList automatically if Management Blade does not give back information of certain Server Blades. (e.g. Server Blade was removed for a short time, network congestion, ...) Host-System does not give back information of certain guest systems. (e.g. network congestion, ...) This deletion causes other Managers to clean up their data, too. For example "Update Manager": Update data (Update Jobs, ...) will be deleted. c) Hints for plink configuration Program plink is necessary for update of: - Management Blade - Connection Blade Program plink is located in Update Repository. For example: ...\BladeSystem\PRIMERGY BX900 Management Blade S1. Program plink is needed by SV Update Manager. The version required is at least 0.74 due to the ciphers supported in current iRMC firmware. Configuration is done via step "Miscellaneous" > section "Plink configuration" of Configuration Wizard: full path of the program plink has to be given. Program plink can be taken from Update Repository (depending on OS of CMS). d) Hint for eLCM updates - Server on which Agentless Service is installed should have iRMC with valid eLCM License Key and SD Card mounted. - iRMC should support eLCM REST API (firmware version > 8.0). 6.11. Diagnostics data collection To collect important diagnosis data scripts are provided: Windows: Call ...\ServerView Suite\cmscollect.bat without any arguments. Result: cmscollect.zip (location is stated in the script output) Please regard that sometimes error messages are displayed for missing files. This is normal because not all files are always present. Linux: Call /opt/fujitsu/ServerViewSuite/svom/ServerView/Tools/cmscollect.sh without arguments. Result: /var/log/fujitsu/ServerViewSuite/cmscollect.tar.gz In order to temporary increase number of logged informations, new trace level can be enabled. Trace level is defined in files in files: Linux: /opt/fujitsu/ServerViewSuite/web/cgi-bin/ServerView/common/serverlistconf.xml (for general ServerList operation) /opt/fujitsu/ServerViewSuite/web/cgi-bin/ServerView/common/browserconf.xml (for browsing/node search process) Windows: C:\Program Files (x86)\Fujitsu\ServerView Suite\ServerView\ServerView Services\scripts\ServerView\common\serverlistconf.xml (for general ServerList operation) C:\Program Files (x86)\Fujitsu\ServerView Suite\ServerView\ServerView Services\scripts\ServerView\common\browserconf.xml (for browsing/node search process) Parameter to be modified: traceLevel The reasonably comprehensive value is traceLevel="6". Restart of ServerList services is required to apply changes.