File Name: dir4.21pf1_windows.fix IBM Director PE Critical Fix - peFix 1 For IBM Director Version 4.21 CONTENTS __________________________________________________________________ 1.0 Overview 1.1 Features or Support Added 1.2 Issues Addressed 2.0 Supported Configurations 2.1 Supported Hardware Configurations 2.2 Supported Operating Systems 2.3 Supported Software Configurations 2.4 Dependencies 2.5 Limitations 3.0 Change History 3.1 Problems addressed by this peFix 3.2 Files Replaced or Added 3.3 peFix Version Information 4.0 Installation 4.1 Install Command Line Syntax 4.2 Package For The Web parameters 4.3 peFix Parameters 4.4 Install Examples 5.0 Uninstallation 5.1 Uninstalling the peFix on IBM Director Agent 5.2 Uninstalling the peFix on IBM Director Server 6.0 Maintenance 6.1 dirpefixtool 6.1.1 dirpefixtool Command Line Syntax 6.1.2 dirpefixtool Parameters 6.1.3 dirpefixtool Examples 6.2 Upgrading to later versions of IBM Director 7.0 Technical Support and Information 8.0 Trademarks and Notices 9.0 Disclaimer 1.0 Overview __________________________________________________________________ 1.1 Features or Support Added Installation of this peFix requires Windows Installer Version 3 to be installed on the target system. The peFix will automatically install Windows Installer Version 3 on the target system if it is not already installed. 1.2 Issues Addressed This peFix addresses problems specific to IBM Director 4.21 support of the IBM eServer xSeries 366, Type 8863 server. 2.0 Supported Configurations __________________________________________________________________ peFix dir4.21pf1 is intended for the configurations listed in this section. This peFix is not for use with other versions of the product and may cause serious functionality problems or data loss if misused. Do not install this peFix on versions or configurations other than those listed in this readme. 2.1 Supported Hardware Configurations dir4.21pf1.exe applies to any hardware running IBM Director Server 4.21 managing an IBM Director Agent on a eServer Xseries 8863 (x366) system or an eServer Xseries 8863 (x366) system running IBM Director Agent 4.21. 2.2 Supported Operating Systems Windows 2000 Server and Advanced Server Editions Windows 2003 Server, Enterprise, Standard, and Web Editions Windows 2000 Professional Windows XP Professional NOTE: Windows 2000 Service Pack 3 is REQUIRED for this patch 2.3 Supported Software Configurations IBM Director 4.21 Server IBM Director 4.21 Agent IBM Director 4.21 Console 2.4 Dependencies Windows 2000 Service Pack 3 2.5 Limitations Administrator privileges are required for the account used to install the peFix. The NOREBOOT option must be specified for the install if using IBM Director software distribution to apply this peFix. Popups may be seen the target system during installation of the patch. These are harmless and can be ignored. After the package has been successfully distributed and applied, the target system must then be rebooted. 3.0 Change History __________________________________________________________________ 3.1 Problems addressed by this peFix The following list identifies problems specific to IBM Director 4.21 support of the IBM eServer xSeries 366, Type 8863 server that are addressed by this peFix. The required level of eServer xSeries 366, type 8863 server BMC firmware is version 1.04. xSeries 366 Intelligent Platform Management Interface (IPMI) issues: o Management Processor Assistant (MPA) Issues: o The Management Processor Assistant (MPA) task in IBM Director Console does not display some environmental sensors. If an out of band alert is generated for any of these sensors, the user will be unable to view that sensor in the MPA GUI. The missing sensors are: - Device Presence sensor for Rack DASDs 0 thru 5 - Device Presence sensor for Rack Power Supply 1 - CPU Mismatch sensors for CPU 1 thru 4 - SAS BP R Detect sensor - Media Detect sensor - CPU PG Status sensor - PCI-X PG Status sensor - SEL Fullness sensor - SIO PG status sensor - MCK Memory Card, SIMM and Link sensors - VRD 1 Hot Sensor - Inv SP Config sensor - Inv R SAS BP Config sensor o IBM Director cannot differentiate the exact component for some alerts that are generated by the xSeries 366 server such as those alerts from fan and power supply events. This is because the sensor label is not available from the Baseboard Management Controller (BMC). This is a sporadic and intermittent problem. o In the system event logs for the BMC, IBM Director incorrectly maps log full events to MPA.Miscellaneous. Log full events should be mapped to MPA.Component.Service Processor.Log. o When the BMC on the xSeries 366 server restarts and disconnects from the MPA task in IBM Director Console, attempts to reconnect it through MPA (right-click ->Auto connect) fail with a Communication Error "Failed to establish connection: Unknown error". Reconnecting is again possible after a delay varying from 30 minutes to 3 hours. o The MPA task displays some sensors which are not supported on the xSeries 366. o The MPA task does not properly interpret several sensors including some power sensors, CPU Mismatch, LED Present, and SEL Fullness. These sensors are not available in the MPA task and not reported through IBM Director events. o System Health/Hardware Status Issues o The IPMI on the xSeries 366 should show four temperature sensors, one for each central processing unit (CPU). These should be monitored as temperature sensors 3,4,5 and 6. However, temperature is only displayed for the first CPU and not for the other three CPUs. o Enumeration and association of power supplies is incorrect. Therefore, IBM Director Console might identify more power supplies than actually exist in an xSeries 366 system. Also, IBM Director can receive false events and alerts for these non-existent power supplies. xSeries 366 Remote Supervisor Adapter II issues: o When disk drives 11 and 12 are removed from an xSeries 366 server, IBM Director incorrectly receives MPA.Unknown events when it should receive MPA.Component.DASD.Removed events. o Various event codes which are new for the xSeries 366 server are not translated by IBM Director. Some new types of alerts are reported as MPA.unknown events with 32-bit hexadecimal. 3.2 Files Replaced or Added For IBM Director Server running on any hardware: chassissystemhealthmapping.properties ESStatusProvider.class ESStatusResourcesNLS.class ESStatusResourcesNLS_en.class eventpublishlist.xml ipmieventmappinglist.xml MPAEventResources.class MPAEventResources_en.class PETEvent.class PETToTWGEventMapper.class PETToTWGMapping.class Connection.class OpaqueConnection.class PhysicalConnection.class ServerConnection.class IPMICommSession.class IPMIResponse.class ReadingUnavailableException.class ReservationInvalidException.class ReservationInvalidException.class EventParsingData.xml CPUTemperatureProvider.class IPMISensorProvider.class SDRProvider.class SDRSensorIdentity.class IPMILogEntry.class SystemLogProvider.class DisplayMappings.class IPMIConstants.class IPMIResources.class IPMIResources_en.class SunWbemProvider.dll For IBM Director Server or IBM Director agent running on an eServer Xseries 8863 (x366) system: sensorsw.dll 3.3 peFix Version Information CompID: 5697NFD00 Release: framework3c Build ID: D0072 APAR: IC45670 4.0 Installation __________________________________________________________________ Running the peFix executable will automatically extract the necessary files to a temporary location and start the installation process. Follow the resulting prompts to complete the installation. 4.1 Install Command Line Syntax dir4.21pf1.exe -s -a [SILENT/UNATTENDED] LOG= VERBOSE DEBUG [NOREBOOT/FORCEREBOOT] 4.2 Package For The Web (PFTW) parameters -a Required by PFTW (-a Must appear before peFix parameters) -s Silent PFTW install 4.3 peFix Parameters SILENT Used for installs with no user interface (assumes unattended) UNATTENDED Used for installs that are unattended but not necessarily silent LOG= Allows user to specify alternate log file location VERBOSE Enable all MSI logging DEBUG Used to turn on higher level of logging NOREBOOT Suppresses reboots requested by the installer FORCEREBOOT Forces the system to reboot once the package installation is finished 4.4 Install Examples Silent Install with reboot: dir4.21pf1.exe -s -a SILENT FORCEREBOOT Unattended Install without reboot: dir4.21pf1.exe -s -a UNATTENDED NOREBOOT Silent install with a debug log: dir4.21pf1.exe -s -a SILENT LOG="c:\peFix.log" DEBUG NOTE: The -a argument must precede all peFix arguments. 5.0 Uninstallation __________________________________________________________________ 5.1 Uninstalling the peFix on IBM Director Agent There is currently no supported method for uninstalling the IBM Director Agent portion of peFixes. It is not required to uninstall IBM Director Agent peFixes before upgrading to a new version of IBM Director. 5.2 Uninstalling the peFix on IBM Director Server In order to upgrade to a later version of IBM Director Server, the IBM Director Server peFix dir4.21pf1 must be uninstalled before upgrading. This can be accomplished through the Add/Remove programs utility within Control Panel. 6.0 Maintenance __________________________________________________________________ 6.1 dirpefixtool A patch utility, dirpefixtool.exe, is available in the \IBM\Director\Support directory. It is a command line executable that can be used to view and manage installed Director peFixes. 6.1.1 dirpefixtool Command Line Syntax dirpefixtool.exe LOG= DEBUG SILENT LIST 6.1.2 dirpefixtool Parameters LOG= Allows user to specify alternate log file location DEBUG Used to turn on higher level of logging SILENT Used for installs with no user interface (assumes unattended) LIST List the Director patches installed 6.1.3 dirpefixtool Examples List all peFixes and write them to the log file C:\Text.log dirpefixtool.exe "LOG=C:\Text.log" LIST 6.2 Upgrading to later versions of IBM Director In order to upgrade to a later version of IBM Director Server, the IBM Director Server peFix dir4.21pf1 must be uninstalled before upgrading. This can be accomplished through the Add/Remove programs utility within Control Panel. It is not required to uninstall IBM Director Agent peFixes before upgrading to a new version of IBM Director. 7.0 Technical Support and Information __________________________________________________________________ IBM Home Page http://www.ibm.com IBM Support Web Site http://www.pc.ibm.com/support IBM Universal Manageability Web Site http://www.pc.ibm.com/us/pc/um/index.html 8.0 Trademarks and Notices __________________________________________________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: AIX, IBM, Netfinity, Netfinity Director, Universal Manageability Services, IBM Director, OS/2, RS/6000, LANClient Control Manager, Remote Deployment Manager, Tivoli IT Director, and Tivoli Management Environment The following are trademarks of their respective owners: Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation IPX, Novell, and NetWare are trademarks of Novell, Incorporated UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited Java and Hot Java are trademarks of Sun Microsystems, Inc Other company, product, and service names may be trademarks or service marks of others. All other brand or product names are trademarks or registered trademarks of their respective holders. 9.0 Disclaimer __________________________________________________________________ THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.