Fujitsu Technology Solutions GmbH ServerView Agents Linux Version 7.00 Release Notes Copyright (c) Fujitsu Technology Solutions 2014 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.2 Configuration 4.3 Startup and Shutdown 4.4 Requirements for Security Configuration 5 OS-specific Issues 5.1 Microsoft Windows 5.2 Linux 5.3 Citrix XenServer 6 Corrigenda of Product Documentation 7 Hints References 1 General This Release Note is a summary of the major extensions, dependencies and operating information with respect to ServerView Agents Linux 7.00 under the Linux operating system with the architectures x86 and x86-64. 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 Agents Linux are a component of the ServerView Suite. The ServerView Suite is supplied for every new PRIMERGY and PRIMEQUEST server and also available per subscription. Contact your Fujitsu Technology Solutions sales representative for ordering details. 1.2 Delivery ServerView Agents Linux are supplied on the ServerView Suite DVD. The contents of this DVD are also available online at support.ts.fujitsu.com/prim_supportcd/start.html 1.3 Documentation The functionality of the ServerView Agents Linux is documented in the ServerView manuals ServerView Suite Installation Manuals ServerView Operations Manager: Installation ServerView Agents for Linux (Installation Guide) You will find this manual at http://manuals.ts.fujitsu.com. 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 Technology Solutions web site ts.fujitsu.com. NOTE: Depending on the PRIMERGY/PRIMEQUEST model or operating system used, some functions of ServerView Agents Linux may differ or may not be implemented! Many functions (e.g. temperature display, fan monitoring) depend on appropriate server control hardware. On PRIMERGYs and PRIMEQUESTs without these facilities, depending functions are not supported. 1.4 License Terms and Conditions ServerView Agents Linux are subject to the general terms and conditions of the Fujitsu Technology Solutions 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 Technology Solutions' 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 Agents Linux consist of six packages in Red Hat Package Manager (RPM) format: srvmagt-agents-7.00-..rpm srvmagt-eecd-7.00-..rpm srvmagt-mods_src-7.00-..rpm SVSystemMonitor-7.00-.noarch.rpm srv-cimprovider-7.00-.x86_64.rpm ServerViewConnectorService-1.20.xx-.i386.rpm and ServerViewConnectorService-1.30.xx-.x86_64.rpm respectively Package Contents and Function =============================================================== srvmagt-agents Fujitsu Software ServerView Agents This package contains ServerView SNMP subagents to provide information about the system to a ServerView Manager: o BIOS subagent (biosagt) o Bus subagent (busagt) o Ethernet Statistics subagent (etheragt) o Hard disk subagent (hdagt) o HP SIM subagent (hpsimagt) o Inventory subagent (invagt) o Operating system subagent (osagt) o Security subagent (securagt) o ServerControl subagent (scagt) *) o ServerControl2 subagent (sc2agt) o Status subagent (statusagt) o Threshold subagent (thragt) o Unix subagent (unixagt) o Update Agent (svupdateagt) o VersionView subagent (vvagt) o VME agent (vmeagt) *) ServerControl subagent (scagt) is deprecated. The version 6.20-xx of ServerView Agents Linux is the last version which supports scagt. This is also true for the corresponding ServerControl MIB (SRVMAGT-SC.TXT) and related OIDs. Each subagent instruments one of the ServerView MIBs which are also included in this package. The subagents use the AgentX protocol to the native SNMP master agent installed with the Net- SNMP package. There are also command line utilities (1) for example for the system's LCD display and external uninterruptible power supply (UPS). This package requires srvmagt-eecd. srv-cimprovider Fujitsu Software ServerView CIM Provider This package contains a number of shared libraries . These libraries implement a CIM management instrumentation for the ServerView extension of the CIM common model. This package requires srvmagt-eecd. srvmagt-eecd Fujitsu Software ServerView eecd Daemon This package contains the Environment and Enclosure Control Daemon (eecd) which gathers information about fans, temperature sensors and other objects across hardware specific interfaces. It detects ServerControl hardware interfaces of the server, collects the available data and keeps them ready for the SNMP subagents at a common hardware independent interface (SCCI). In addition there are command line utilities (1) for external RAID support. This package is required by srvmagt-agents and srv-cimprovider. This package requires srvmagt-mods_src. srvmagt-mods_src Fujitsu Software ServerView Modules The srvmagt-mods_src package contains the source code of the optional ServerView module smbus offered for specific server models or specific Linux distribution. It extends the kernel to access ServerControl hardware. This package is required by srvmagt-eecd. SVSystemMonitor Fujitsu Software ServerView System Monitor This package allows you to monitor and check the following server information locally on your server: o Environment information, including fan and temperature sensor information. o Power supply information. o Mass storage information. This information is only available if ServerView RAID Manager is installed on the system. o System board information. o Network information. o Driver Monitor information. o Update Status of Firmware and Driver This package requires srvmagt-eecd and ServerViewConnectorService. ServerViewConnectorService Fujitsu Software ServerView Remote Connector Service This package contains the ServerView Remote Connector Service that consists of a daemon listening for incoming requests and providers started to fulfill those requests. Such providers are included for example in the package srvmagt- eecd. This package is required by srvmagt-eecd and SVSystemMonitor. --------------------------------------------------------------- 1) The packages contain the following command line utilities. o eecdcp(8) eecd control program o lcdisp(8) configure text on the LCD o meclear(8) reset memory module error counters o oemups(8) configure an external UPS o srvmagt(8) handle package maintenance tasks o SVreadLog(8) display the ServerView Message Log o SVclearLog(8) (save and) clear the ServerView Message Log o SVforceVV(8) tell vvagt to do an immediate rescan o PrimeCollect(8) collect relevant system Service Data =============================================================== 2.2 Hardware 2.2.1 Supported Hardware See http://support.ts.fujitsu.com/com/support/downloads.html 2.2.2 Required Hardware The ServerView System Monitor has a built in functionality to output alarm sounds when errors occur. These alarm sounds can only be output on systems which have a built in pc speaker. You can check if the alarm sound is working by clicking on the "Test" button in the alarm tab of the option dialog window of the ServerView System Monitor. 2.3 Software 2.3.1 Supported Software (OS) See http://support.ts.fujitsu.com/com/support/downloads.html 2.3.2 Required Software ServerView Agents Linux operate on x86 and x86-64 architectures in suitable software configurations. Before the ServerView agents are installed, make sure that the relevant net-snmp packages including utilities are installed in accordance with the operating system platform. Furthermore ServerView Agents Linux require that the GNU standard C++ library and openssl software packages are installed on the target Linux distribution with a version suitable for this distribution. On systems running SUSE or Red Hat Linux a libcurl package is also required. Novell/SUSE The naming of the packages depends on SLES Version and architecture: SLES11 libstdc++33 libopenssl0_9_8 libcurl4 SLES12 libstdc++33 openssl curl Red Hat V7 libstdc++ openssl libcurl Red Hat less V7, Oracle Linux, Citrix Xen Server compat-libstdc++-33 openssl libcurl (RedHat only) These dependencies are usually checked during installation via srvmagt(8). Note: On Oracle VM Server 3.0 (and higher) not all of those packages are available by default. Oracle provides a document that describes the process to resolve those dependencies. It can be found on My Oracle Support with Doc-ID 1351534.1. Please follow the instructions provided in the document before ServerView Agents are installed. My Oracle Support can be accessed by customers with a valid support contract. Additional requirements for SVSystemMonitor: o A graphical desktop environment based on X11. Supported are KDE and GNOME. o An appropriate Java Runtime >= V1.6.0_21. It is recommended to use the Java Runtime provided on the ServerView Suite DVD. o For viewing RAID information the ServerView RAID Manager has to be installed and must be running. o For viewing the online help pages a web browser must be installed. Additional requirements for srv-cimprovider: o ServerView CIM Provider are 64-bit binaries and operate therefore only on x86-64 architectures. o A CIMOM (CIM Object Manager) service must be available. Supported CIMOMs are SFCB and OpenPegasus. On systems running SUSE or Red Hat Linux, where PLDP or DUP is not applicable, the following packages are also required: kernel-source/-devel Include files for module compilation binutils C compiler utilities gawk To process modules before compilation gcc GNU C compiler glibc-devel C compiler libraries 3 Changes See http://support.ts.fujitsu.com/com/support/downloads.html 4 Product Installation, Configuration, Start-up When installing ServerView Agents Linux, 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 ServerView Agents Kernel Modules -------------------------------- ServerView Agents Linux operate generally with (loadable) kernel modules supplied for the underlying system via the processes established for other kernel modules. These processes include the PLDP [1] for SLES (starting from version 10) and the DUP [2] for RHEL (starting from version 5). For environments that do not support PLDP or DUP, ServerView Agents Linux offer to install loadable kernel modules that are compiled during installation unless the system prohibits the use of such modules. NOTE: Compile errors usually indicate that kernel source is not installed or inappropriate for the running kernel. If you want to compile the module later, call /etc/init.d/eecd_mods_src start as root. The call /etc/init.d/eecd_mods_src status returns additional information about the modules. Successful compilation requires installed kernel source and GCC development tools. NOTES: o On PLDP or DUP enabled systems, ServerView Agents Linux will first try to load the ServerView kernel modules via the PLDP or DUP facilities. See the notes on PLDP [1] and DUP [2] for more information how to manage modules with these processes. If this fails, or for environments that do not support PLDP or DUP, ServerView Agents Linux offer to compile the ServerView modules during installation unless the system prohibits the use of such modules. o If the version of the installed ServerView kernel modules is not appropriate, ServerView Agents Linux try an update of the modules. On SLES10 an update of a single package is not possible. This may lead to an update of the whole system (depending on the enabled software repositories). o ServerView Agents Linux do not offer smbus module when installed on Citrix XenServer or OVM. Depending on the underlying hardware this may result in restricted functionality, for example the CPU prefailure detection and analysis (CPU PDA). o For PRIMEQUEST server no smbus module is provided. Script-based ServerView Agents Installation ------------------------------------------- The installation script srvmagt offered with ServerView Agents Linux simplifies the task of RPM package installation and deinstallation, reduces the amount of command typing and thus lowers the error probability. The approach to just use the rpm(8) command is still available for user customization with individual scripts. 4.1.1 Installation and Deinstallation using the srvmagt Install Script The srvmagt installation script checks if the target system satisfies the necessary requirements, tests dependencies and configuration and calls the rpm(8) commands that actually installs or removes the packages. For further details consult the srvmagt(8) manual page. To install ServerView Agents Linux ---------------------------------- 1. Become root and establish the runtime requirements for ServerView Agents Linux operation (see section 2.3). 2. Edit the snmpd configuration file to introduce the entries necessary for ServerView Agents Linux, particularly the IP addresses of systems that are permitted to issue SNMP requests or receive SNMP traps. 3. Enable access to the packages of the ServerView Agents Linux by mounting the ServerView Suite DVD and change to folder /SVSSoftware/Software/ServerView/Linux/Agents/srvmagtDVD.sh with the packages. 4. Download (copy) the script srvmagt_DVD.sh from DVD to /tmp 5. Open (as root) a terminal and call cd /tmp sh srvmagt_DVD.sh To deinstall ServerView Agents Linux ------------------------------------ 1. Become root 2. Call srvmagt remove 4.1.2 Installation and Deinstallation using the rpm(8) Command To install ServerView Agents Linux ---------------------------------- 1. Become root 2. Mount the ServerView Suite DVD supplied with every PRIMERGY/PRIMEQUEST server and change to directory /SVSSoftware/Software/ServerView/Linux/Agents. 3. Install the following RPM packages rpm -U srvmagt-mods_src--..rpm rpm -U ServerViewConnectorService--..rpm rpm -U srvmagt-eecd--..rpm rpm -U srvmagt-agents--..rpm rpm -U SVSystemMonitor--.noarch.rpm rpm -U srv-cimprovider--.x86_64.rpm in the order given. Get the and number for the ServerView Agents Linux as appropriate. Installation of ServerView Agents Linux automatically stops and then restarts the SNMP master agent snmpd. To deinstall ServerView Agents Linux ------------------------------------ 1. Become root 2. Deinstall the following RPM packages rpm -e srv-cimprovider rpm -e SVSystemMonitor rpm -e srvmagt-agents rpm -e srvmagt-eecd rpm -e srvmagt-mods_src rpm -e ServerViewConnectorService in the order given because of the internal package dependencies. 4.2 Configuration 4.2.1 General System Configuration This section lists general system configuration options to choose or apply. o System time and timezone information must be configured correctly to the local time at the location where the system operates. Otherwise, scheduled Power ON/OFF might not occur at the configured points in time. Consult hwclock(8) to see how to configure the CMOS clock and/or system time to local time as necessary. 4.2.2 Configuring the Native Net-SNMP Agent There are numerous places that configuration files can be found and read from (see snmp_config(5)). By default, the configuration file /etc/snmp/snmpd.conf is used. To specify specific rights, write access or trap destinations extend this configuration file. You can edit the configuration file with a text editor such as vi(1). Information about the syntax is in snmpd.conf(5). You should specify the following directives Variable Explanation =============================================================== syscontact } Values for the corresponding variables syslocation } in the MIB-II system group --------------------------------------------------------------- authtrapenable En/disable authentication failure traps --------------------------------------------------------------- Net-SNMP offers several mechanisms to protect the implemented instrumentation against unauthorized use: 1. requests are only accepted from preconfigured stations 2. requests are only accepted with correct preconfigured community string 3. subtrees of the OID tree can be protected against unauthorized access. This is a template for a configuration that allows ServerView SNMP get requests. Set / according to your environment (see snmpd.conf(5)). This example uses IPv4 addresses, use IPv6 addresses if and where needed. com2sec svSec localhost public com2sec svSec 127.0.0.1 public com2sec svSec / public group svGroup v1 svSec view svView included .1 access svGroup "" any noauth exact svView none none NOTE: The order of com2sec definitions is significant. It goes from specific IP addresses to generic IP addresses within the same community. NOTE: This configuration disables ServerView SNMP set requests. To modify values or shutdown the server from the ServerView manager replace the 'access' line above by access svGroup "" any noauth exact svView svView none NOTE: The community name in the example is "public". If you want to use another community name for security reasons, replace "public" with your chosen name. In this case configure the community name also in the ServerView components on the manager side. To specify the destination addresses for SNMP traps (where a ServerView manager is running) add for each target a line like trapsink [ [port]] with the target's IP addresses or host name and the chosen community (see snmpd.conf(5)). NOTE: ServerView Agents Linux include the entries ### BEGIN srvmagt-- master agentx ### END srvmagt-- into /etc/snmpd.conf. These are necessary for their correct function. 4.2.3 Configuring the ServerView Agents Linux The configuration file for the ServerView Agents Linux is now /etc/srvmagt/config. Lines starting with '#' are comments, other lines have the format = with values defined for as follows. NOTE: Changes made to the configuration file will take effect after restarting ServerView Agents Linux. o AgentPermission If set to 3, it is possible to modify ServerView values via SNMP set requests. This is required in addition to allowing SNMP set requests in snmpd.conf as described above. o AgentShut If set to 3, it is possible to shutdown/reboot the system via SNMP set requests. This is required in addition to allowing SNMP set requests in snmpd.conf as described above. o NoAccountCheck If set to something other than zero, no password checking is performed on ServerView set requests. The default is zero, i.e. password checking is enabled (see UserGroup). o UserGroup The ServerView Operations Manager requires authentication with a user/password before it executes SNMP set requests. The user has to belong to the group specified by UserGroup. If this variable is missing, the group bin is taken, i.e. the group the user root belongs to. If you want to use a separate user account for ServerView, make sure it belongs to the group bin or add this entry to /etc/srvmagt/config. o ShutdownDelay Specifies the time (in minutes) between an SNMP shutdown request and the actual shutdown. o ScanTapeDevices If set to something other than zero, the tape devices /dev/nst* are opened in order to get their current status. The opening of the tape device might cause (depending on the driver) an unintentional change of its read/write position. If the tape device is shared among servers, this parameter makes sure that ServerView does not impact tape operations (e.g. backup) by state queries. The default is zero, i.e. tape devices are not opened. o TraceFileLimit An integer value greater than zero indicates the size of the automatic circular log buffer in certain multiples, default is 1 (small). Values greater than 2 (medium) are reduced to 2. The value 0 (zero, none) disables automatic logging. o InventoryRescan Specifies the period (in minutes) in which the inventory is rescanned. Possible values: 0, 120..34560 The value 0 disables rescan. Values between 1 and 120 are set to 120. Values greater than 34560 are set to 0. If InventoryRescan is missing, the rescan is performed every 120 minutes. To support the performance and threshold manager for virtual hosts (Citrix Xen or Xen) in the ServerView Operations Manager, it is necessary to configure account information for the server within ServerView VME agent. In order to do so, the following steps are necessary: 1. Edit the text file /etc/srvmagt/VME/etc/app.config.xml 2. Search for the section titled 3. Fill in user and password information as necessary (e.g. us123123passwd) NOTE: The password is in plain text, so you must limit access to this file and you should not use a privileged user. 4. Save the file 5. Restart ServerView Agents NOTE: KVM virtual hosts don't require username and password. 4.3 Startup and Shutdown The ServerView Agents Linux can be started or stopped following the familiar concepts. NOTE: The SNMP master agent snmpd must be running to start ServerView Agents Linux To start ServerView Agents Linux 1. Become root 2. Run srvmagt start -- or 2. Run /etc/init.d/eecd_mods_src start 3. Run /etc/init.d/eecd start 4. Run /etc/init.d/srvmagt start 5. Run /etc/init.d/srvmagt_scs start To stop ServerView Agents Linux 1. Become root 2. Run srvmagt stop -- or 2. Run /etc/init.d/srvmagt stop 3. Run /etc/init.d/eecd stop 4. Run /etc/init.d/eecd_mods_src stop The ServerView Environment and Enclosure Control Daemon (eecd) maintains the software watchdog implemented in firmware depending on the hardware model. The software watchdog is enabled/disabled during the command /etc/init.d/eecd start/stop and periodically refreshed ("heart-beat") by the eecd daemon. NOTE: The script kills the eecd daemon hard 90 secs after an unsuccessful attempt to terminate it gracefully. In such a situation, the software watchdog might not be cleared properly. If it is enabled with reboot option, the system will reboot when the watchdog timer expires. ServerView Agents Linux integrate themselves into the system's automatic startup sequence. If ServerView Agents Linux is installed using rpm commands, you have to enable automatic startup of the native SNMP master agent. Starting the ServerView System Monitor ServerView System Monitor can be started by entering the command "ssm" in a terminal window on the KDE or GNOME desktop. When starting the ServerView System Monitor for the first time you will see a login prompt. Here you have to enter the user name and the password of a user with administrative privileges on the target server. This user has to belong to one of the following user groups: o The group "bin" or o The group which is configured as ServerView Agents UserGroup (see section 4.2.3). Start and Stop of the CIM Provider is done by the CIMOM. For startup and shutdown of the CIMOM see the documentation of the respective CIMOM. 4.4 Requirements for Security Configuration ServerView Agents Linux use local interprocess communications via the Linux socket interface (see socket(7)) in the PF_UNIX and PF_INET domains (see unix(7)) to the SNMP master agent snmpd (this is part of AgentX), and to the eecd daemon. They use also SNMP requests to communicate to each other (via the local SNMP master agent snmpd) by using "localhost" as target address. On PRIMERGY BX models they use also SNMP requests to communicate to the Management Blade (MMB). They take the SNMP community from the first "com2sec" entry in the corresponding snmpd.conf file that contains the source address "localhost". If no such entry exists, the community defaults to "public". NOTE: If you changed the community in the snmpd configuration file and restarted snmpd, restart also ServerView Agent Linux (see previous section). RECOMMENDATION: If you use a nonstandard community within a blade server, then configure the same community string in all blades and MMBs within the same chassis. If a firewall or other measure to control interprocess communications is activated on your server, o allow SNMP ports 161 and 162: Incoming (or internally originating) packets on port 161 (service name: snmp) MUST BE accepted, corresponding replies MUST be allowed. For SNMP trap sending you MUST allow outgoing packets on port 162 (service name: snmptrap), at least for protocol UDP. o allow ServerView ports 3172 and 3173: Incoming (or internally originating) packets on these ports MUST BE accepted, corresponding replies MUST be allowed. Port 3172 is used by he ServerView Remote Connector to listen for incoming requests from various ServerView Suite components, including the ServerView Performance Manager, Configuration Manager and Power Manager. Port 3173 is used by the ServerView eecd daemon to listen for status information from the ServerView RAID daemon. o allow CIM server ports 5988 and 5989: Ensure that the CIM server can use the default TCP/IP port 5988 for HTTP or 5989 for HTTPS. o allow "localhost" (with IPv4: 127.0.0.1) local interprocess communications using the Linux socket interface in the PF_UNIX and PF_INET domain MUST be enabled. The following command lines give an example how to change the configuration of the Linux kernel firewall iptables (see also iptables(8)) to unlock the necessary communication paths for ServerView Agents Linux: # Create a new user defined chain called "ServerView-INPUT" /sbin/iptables -N ServerView-INPUT # Add three rules to the new chain. These rules allow to # accept packages with port number 161, 3172, and 3173 /sbin/iptables -A ServerView-INPUT -p udp -m udp --dport snmp -j ACCEPT /sbin/iptables -A ServerView-INPUT -p tcp -m tcp --dport 3172 -j ACCEPT /sbin/iptables -A ServerView-INPUT -p tcp -m tcp --dport 3173 -j ACCEPT # Add the new chain to the INPUT-filter table. Putting it to # the top of the table ensures the rules are applied first. /sbin/iptables -I INPUT 1 -j ServerView-INPUT # Save the modified iptables configuration into a file /sbin/iptables-save > iptables.new # Overwrite the current configuration to establish the # modification of the firewall configuration after a # system reboot cp iptables.new /etc/sysconfig/iptables 5 OS-specific Issues 5.1 Microsoft Windows Not applicable. 5.2 Linux This section lists incompatibilities in ServerView Agents Linux 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/PRIMEQUEST systems, their components and the operating systems. See corresponding README files. o For the driver monitor functionality on SUSE it is necessary to extend the syslog-ng configuration file. Due to a bug in SLES11 it is possible, that the AppArmor profile /etc/apparmor.d/sbin.syslog-ng contains an invalid statement after this change: @{CHROOT_BASE} = , This has to be changed to @{CHROOT_BASE} = "" o The OID sniInterfaceAdapter always returns an empty string. o The BIOS agent does not report serial/parallel interface settings. o The transmission speed of an Ethernet interface is often reported as 10 Mbit/s. This is part of the MIB-II functionality within the SNMP subsystem. Interpret this value as "at 10 MBit/s or more". o The PCI device number is returned as value for the PCI Slot number instead of the actual physical slot number for those systems that do not support the PCI IRQ Routing Table Specification in their SMBIOS. o For some SCSI and RAID adapters, the driver name associated with the adapter cannot be correctly decoded. Instead, the Ids for PCI vendor, device and revision appear as "UNKNOWN (V:/D:/R:)". o The scan for the S.M.A.R.T. information is currently disabled in the hard disk agent (hdagt). Appropriate information is supplied by the corresponding RAID software. o The ServerView ServerControl Agent (scagt) accepts set requests for certain OIDs with values that are not supported by the underlying ServerControl processor, for example for watchdog timeouts. Such invalid values are actually not set. 5.3 Citrix XenServer o Installation of ServerView Agents on Citrix XenServer is offered via the XenServer Supplement CD. It includes the necessary software packages, scripts that support installation and configuration and release documentation. 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 VMware ESX is no longer supported. o In SSM Update Configuration tab -> Download Settings tab, only HTTP protocol is available. o ServerControl subagent (scagt) is deprecated. The version 6.20-xx of ServerView Agents Linux is the last version which supports this subagent. This is also true for the corresponding ServerControl MIB (SRVMAGT-SC.TXT) and related OIDs. o ServerView Agents Linux do no longer support virtual machines (VM). o For proper functionality of the installation script srvmagt(8), use ONLY pathnames that DO NOT contain spaces or special characters. o IPv6 support is restricted in the following aspects: - Management controllers and Uninterruptible Power Supplies (UPS) with IPv6 addresses are not yet supported o ServerView Agents Linux and the eecd daemon place their core files into the root directory "/", unless the maximum core file size is set to 0. To set the maximum core file size 1. Become root 2. Call ulimit -c You should set to "unlimited". o For proper functionality of the VME agent make sure that Xen API is enabled. o If you want to edit the partition table of a hard disk via YaST there may occur an error when YaST wants to write the new partition table. This is caused by the SCSI agent which has tried to read the partition table in the meantime. To temporarily stop the SCSI agent 1. Become root 2. Run /etc/init.d/srvmagt stop hd 3. Edit the partition table with YaST 4. Run /etc/init.d/srvmagt start hd o If hardware or storage extensions are added to the server and ServerView Agents Linux do not recognize the changes, a rescan of the all hardware modules could solve the problem. To rescan all hardware modules 1. Become root 2. Run /etc/init.d/eecd stop 3. Run /etc/init.d/eecd rescan 4. Run /etc/init.d/srvmagt restart o On Red Hat Linux startup, the mouse controller function is initialized with an init script that runs after the ServerView Agents Linux were initialized. It will thus not be visible in ServerView until the next device scan after (at most) 10 minutes. o If you need to have installed different versions of Java at the same time then please make sure the link /usr/bin/java points to the correct Java version for the SVSystemMonitor. Please also check the PATH variable for Java references and, if set, the contents of the JAVA_HOME variable. References User documentation for the PLDP and DUP and generally for drivers in PRIMERGY servers is available as: [1] Novell Partner Linux Driver Process for PRIMERGY servers ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html [2] Red Hat Driver Update Process for PRIMERGY servers ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html [3] Linux drivers for PRIMERGY servers ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html #