Director BK Troubleshoot

IBM Systems
IBM Systems Director Troubleshooting and Support Guide

Version 6.2
GC30-4177-04
IBM Systems

Version 6.2
GC30-4177-04
Note Before using this information and the product it supports, read the information in Notices on page 283.
Copyright IBM Corporation 1999, 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this publication . . . . . . . . ix
Conventions and terminology . . . . . . . . ix Publications and related information . . . . . . ix Web resources . . . . . . . . . . . . . xii How to send your comments . . . . . . . . xiii IBM Systems Director Server might fail to start in IPV6-only environment on Linux platform . . . Tables are not displayed correctly . . . . . . The cimserver service stops . . . . . . . . Unable to filter events for virtual server failures Unable to run more than two smcli commands simultaneously . . . . . . . . . . . . User with a blank password cannot perform operations on Windows systems . . . . . . Virtual farm events are not filtered . . . . . Virtual farm view does not refresh when hosts change . . . . . . . . . . . . . . . Virtual server becomes unusable during relocation . . . . . . . . . . . . . . Virtualization manager tasks fail to start in multi-NIC environment . . . . . . . . . Add or Remove Programs displays an incorrect program size for Platform Agent . . . . . . Antivirus programs might conflict with certain IBM Systems Director processes . . . . . . Receiving alerts associated with an LSI 1030 Controller . . . . . . . . . . . . . . Incorrect version listed for Common Agent 6.2.0.1 on AIX . . . . . . . . . . . . . . . Cannot restart the OS for managed AIX 6 CAS Update manager limitations and workarounds . Installation and migration troubleshooting . . . . AIX installation troubleshooting . . . . . . Linux installation troubleshooting . . . . . . VMware installation troubleshooting . . . . . Windows installation troubleshooting. . . . . Cannot connect to agents after migration from 6.1.x to 6.2 . . . . . . . . . . . . . . Agents are not migrated during migration from 6.1.x to 6.2 . . . . . . . . . . . . . . Cannot install agent on managed system . . . Installing a version of IBM Systems Director that is earlier than the current version . . . . . . IBM Systems Director installation hangs and then fails . . . . . . . . . . . . . . . . IBM Systems Director installation or uninstallation fails and requires cleanup . . . . Network outage while installing IBM Systems Director Server . . . . . . . . . . . . Installation fails when contacting an agent manager . . . . . . . . . . . . . . Uninstallation of Common Agent on SUSE Linux Enterprise Server 9 for System x takes approximately one hour . . . . . . . . . Silent installation does not verify settings before installing . . . . . . . . . . . . . . Configuration data is not preserved after uninstalling IBM Systems Director on Linux on System x . . . . . . . . . . . . . . 12 13 13 13 14 14 14 15 15 15 16 16 17 17 18 18 26 26 27 29 30 31 31 32 33 34 35 37 38
Troubleshooting and support . . . . . 1

Limitations and workarounds. . . . . . . . . 1 Discovery profile auto-unlock and auto-inventory not supported for IBM Director Agent . . . . . 1 Agent installation does not generate events . . . 2 BladeCenter is offline after the AMM failed over . 2 Changes to the network interface card (NIC) configuration cannot be deployed to operating system resources . . . . . . . . . . . . 2 Command fails on smcli . . . . . . . . . 2 Date and time remain editable after deselecting the Power On Server . . . . . . . . . . 3 Delete operations take a long time to complete . . 3 Error messages include placeholder text . . . . 4 Completion status for the Send a numeric page event action is incorrect. . . . . . . . . . 4 Excessive windows prompting for undoable disk power actions . . . . . . . . . . . . . 4 File Manager displays a blank table. . . . . . 4 File Manager fails to copy files larger than 1.5 GB 5 Help selection is a question mark . . . . . . 5 IBM Storage Configuration Manager (SCM) 2.10 or earlier does not support non-English operating systems . . . . . . . . . . . . . . . 6 Limitations using IBM Systems Director to manage resources behind a NAT firewall . . . . 6 Capacity information is not correct for storage devices . . . . . . . . . . . . . . . 7 JAWS screen reader does not indicate that an update has taken place . . . . . . . . . . 7 Multi-Switch Interconnect Module (MSIM) vital product data is missing from inventory . . . . 7 Table view entries do not include Linux operating system version information . . . . . . . . 7 Event Filter Builder tree displays multiple Windows event log nodes . . . . . . . . . 8 The OID for different SNMP traps are the same . 8 Removing a managed operating system does not remove the managed server . . . . . . . . 8 Limitations of large tables . . . . . . . . . 9 Selections or data entered into fields is lost . . . 9 Severe log entry in the trace log . . . . . . 10 The Severity column always reports Information 10 Warning message recorded after installing the SMbus or LM78 device driver . . . . . . . 10 Switch does not respond to IP address change . . 11 Switch information is not accurate in IBM Systems Director Server . . . . . . . . . 11
38 39
39
Copyright IBM Corp. 1999, 2010
iii
CIT service error displayed in Event Viewer when installing CAS agent on Windows Server 2008 . . . . . . . . . . . . . . . . A return code with no message text is displayed when deploying Windows agent packages . . . Service processor troubleshooting . . . . . . . Service processor is unresponsive . . . . . . Enabling hardware events . . . . . . . . Unknown error message is displayed when using SLES . . . . . . . . . . . . . . . . Database configuration troubleshooting . . . . . Errors occur during the Oracle Database configuration . . . . . . . . . . . . . ORA-00604 error from the Oracle Database . . . Oracle Database 10g Release 2 administrator client will not install on Red Hat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10 . . . . . . . . . . . . . . Oracle Database 10g Release 2 administrator client installation on Linux on Power Systems throws errors . . . . . . . . . . . . . Unable to connect to the database . . . . . . Database data is not displayed after database restart . . . . . . . . . . . . . . . Poor Performance when the IBM Systems Director server is configured with Microsoft SQL Server 2005 configuration. . . . . . . . . smrestore fails when IBM DB2 is configured to require approval of restore operation . . . . . Unable to access Log in page for IBM Systems Director . . . . . . . . . . . . . . . Logging into IBM Systems Director Server fails . . IBM Systems Director Server troubleshooting . . . An IBM Systems Director Server manageable resource shows offline after discovering its agent . IBM Systems Director Server fails to start . . . IBM Systems Director causes network traffic . . IBM Systems Director Server not receiving event indications. . . . . . . . . . . . . . Problems exist on IBM i systems with IBM Director Agent version 5.20 installed . . . . . Trace and error log files are not created . . . . Uncertain if IBM Systems Director Server is running. . . . . . . . . . . . . . . User is locked out of IBM Systems Director. . . Common Agent and Platform Agent troubleshooting Extraneous CIM indication errors appear in the system log on Linux . . . . . . . . . . Managed resource does not send events . . . . You cannot promote Platform Agent to Common Agent on Linux with Xen. . . . . . . . . Cannot install agents on Red Hat Enterprise Linux or VMware managed systems using the Agent Installation Wizard . . . . . . . . Cannot install agent on managed system . . . Common Agent cannot be installed on an AIX or Linux system . . . . . . . . . . . . . Installing Common Agent on managed systems with IBM Director Agent version 5.20 does not succeed . . . . . . . . . . . . . . .
39 40 40 40 42 43 44 44 44
45
47 48 49
50 51 52 52 54 54 55 55 56 56 57 57 58 59 59 59 60
60 61 62
63
A discovered agent displays an unexpected managed system. . . . . . . . . . . . Unable to upgrade L2 agent to Common Agent on VMware ESX Server 3.5 or Red Hat Enterprise Linux 5.3 hosts . . . . . . . . . . . . IBM Systems Director, version 6.1.1, Platform Agent installed on systems with an Integrated Management Processor (iMM) requires an Intelligent Platform Management Interface (IPMI) driver . . . . . . . . . . . . . . . Platform Agent 5.20.3x installation fails on systems with Citrix XenApp . . . . . . . . Common Agent does not start when the host name is set to localhost or the name server is not setup correctly . . . . . . . . . . . . Installation of the common agent on AIX fails to start LWI . . . . . . . . . . . . . . IBM Director Agent version 5.20.x agents automatically change to offline state in IBM Systems Director 6.x . . . . . . . . . . Web interface troubleshooting . . . . . . . . Add Criterion window stops updating . . . . Certificate has not been signed by a trusted authority . . . . . . . . . . . . . . Firebug Firefox extension might cause unpredictable behavior in the IBM Systems Director Web interface . . . . . . . . . . Internet Explorer fails to display the IBM Systems Director Web interface . . . . . . . Login message displays corrupt characters . . . Navigation pane is not displayed correctly during initial log in. . . . . . . . . . . No results found when using Find a Resource . . Panels display translated text in multiple languages . . . . . . . . . . . . . . Panels display truncated text in non-English languages . . . . . . . . . . . . . . Pop-up window does not close . . . . . . . Security certificate is not valid . . . . . . . Unpredictable results occur when two users log into IBM Systems Director Server using the same browser application. . . . . . . . . . . Unable to connect to Web interface with SUSE Linux Enterprise Server 10 . . . . . . . . Unable to export information . . . . . . . Unable to print information . . . . . . . . The IBM Systems Director Web interface does not perform as expected when browsing . . . . . Welcome page is not displayed during initial log in. . . . . . . . . . . . . . . . . Columns are empty in Navigate Resources . . . Launched tasks troubleshooting . . . . . . . Contents of the launch[x].jnlp file are displayed A download window is displayed . . . . . . Empty window is displayed or nothing happens A host name mismatch is detected. . . . . . Java Web Start - Download Error window is displayed . . . . . . . . . . . . . . Java Web Start fails because correct IP address cannot be determined . . . . . . . . . .
64
64
65 65
66 66
67 67 67 67
70 70 70 71 71 71 72 72 73
74 74 74 75 76 77 78 78 78 79 80 81 82 83
iv
Java Web Start fails due to JARS signed with multiple certificates. . . . . . . . . . . 83 Launched-tasks feature fails on System z system 84 Message indicates a failure to validate certificate 85 Message indicates that the applications digital signature has an error . . . . . . . . . . 85 Message indicates that the installation image for console cannot be found . . . . . . . . . 86 Message states that Java Web Start is required . . 87 Multiple Firefox browser windows open. . . . 87 Opening launch.jnlp window is displayed . . . 87 Storage application launch failure information . . 88 Unable to display the requested help . . . . . 89 Unable to launch the application . . . . . . 89 Unable to load resources . . . . . . . . . 92 Windows fails to open a file . . . . . . . . 93 Accessibility troubleshooting, including JAWS . . . 93 Accessible method for installing IBM Systems Director . . . . . . . . . . . . . . 93 Preventing session timeouts for users with disabilities . . . . . . . . . . . . . . 94 Audible notification is not supported in Internet Explorer . . . . . . . . . . . . . . 94 Create Virtual Server wizard displays previous page when pressing Enter in a text field . . . . 95 Cursor disappears and page refreshes when performing virtualization manager tasks. . . . 96 Focus is lost when clicking the Select All or Deselect All button . . . . . . . . . . . 96 Identifying table filter row information using JAWS . . . . . . . . . . . . . . . 97 JAWS screen reader becomes mute . . . . . 97 JAWS does not read Pre-Installation Utility content . . . . . . . . . . . . . . . 98 JAWS screen reader reads extra frame . . . . 98 JAWS cannot read remote serial console output 98 JAWS screen reader reads some Web interface elements incorrectly . . . . . . . . . . 99 JAWS screen reader suggests incorrect keys for radio buttons in a table . . . . . . . . . 100 JAWS screen reader reads the Next button incorrectly on some pages . . . . . . . . 100 Keyboard navigation does not work in or between Selected and Available list boxes . . . 101 Keyboard navigation does not work in some Action menus . . . . . . . . . . . . 101 Language attribute not set properly in some panels when using Internet Explorer . . . . 101 The calendar is not usable or readable by the JAWS screen reader in forms mode . . . . . 102 The Time field is not readable by the JAWS screen reader . . . . . . . . . . . . 102 Unable to navigate to expanded content with traditional key sequences when using JAWS screen reader . . . . . . . . . . . . 102 Unable to select table row using JAWS screen reader in Internet Explorer . . . . . . . . 103 Automation manager troubleshooting . . . . . 103 A program fails to run when the event automation plans is triggered . . . . . . . 103
Active Energy Manager threshold options are not displayed in the Event Automation Plan wizard . . . . . . . . . . . . . . The specified event does not trigger the event automation plan . . . . . . . . . . . An event automation plan is not triggered when the event filter uses extended details . . . . An SNMP trap or an SNMP inform request was not received . . . . . . . . . . . . . Automation plan not activated for virtual farm or relocation event. . . . . . . . . . . Cannot run Collect Inventory task using an event action . . . . . . . . . . . . . Difficulty accessing event automation plan system variables . . . . . . . . . . . E-mail fails to be sent. . . . . . . . . . Event actions fail . . . . . . . . . . . Target systems are lost when an event automation plan is imported . . . . . . . Event automation plans are not displayed . . . Event automation plans do not support some features of earlier event action plans. . . . . Event automation plans do not work correctly Event not forwarded to Tivoli Enterprise Console event server . . . . . . . . . . Group members are not processed correctly in static groups. . . . . . . . . . . . . IBM i message queue events do not trigger event automation plans as expected . . . . . News fails to post to a newsgroup . . . . . Resource-monitor threshold settings change unexpectedly . . . . . . . . . . . . SNMP traps do not contain message text . . . Start a program on a system event action fails Test results are missing for an event action . . Threshold values are no longer selected or are zeroed out in an event automation plan . . . Unfamiliar event filters are displayed on the Event Filters page . . . . . . . . . . . Configuration manager troubleshooting . . . . Configuration manager status is shown as Not Ready in the Welcome page . . . . . . . Mass configuration fails to configure Asset ID information . . . . . . . . . . . . . Deploy of a configuration template fails on a target device that is not supported . . . . . Discovery manager (including inventory) troubleshooting. . . . . . . . . . . . . Discovery troubleshooting . . . . . . . . Inventory troubleshooting . . . . . . . . Security and requesting access troubleshooting . . Access request to IBM Director Agent 5.20 fails SNMP remote service access point of a switch goes offline after switch creation and stays offline after request access . . . . . . . . Request Access password length restriction . . Access request to a managed system running SUSE Linux Enterprise Server fails . . . . . Agentless or Platform-Agent managed resource cannot be accessed . . . . . . . . . . Managed resource state is Unknown . . . . .
Contents
104 104 105 107 108 110 110 110 111 111 112 113 113 114 114 115 116 116 117 118 118 119 119 120 120 122 122 123 123 137 139 139
141 141 142 143 143
Credential mapping wizard does not finish when editing a credential mapping . . . . . Settings permission is not available to users in groups other than smadmin . . . . . . . Hardware Management Console access state becomes unknown after supplying incorrect credentials . . . . . . . . . . . . . Trust domain users cannot log on . . . . . Spaces are not allowed for LDAP user full DN LDAP users unable to login when users in same path exceed 500 . . . . . . . . . . . DN values for securityldap.properties must match the LDAP server base values . . . . . IBM BladeCenter and System x management troubleshooting. . . . . . . . . . . . . Access is not granted automatically to switches IBM Systems Director cannot communicate with out-of-band systems . . . . . . . . . . The server reports that "Power off and Restart" was successful, but it was not . . . . . . . Full access to a QLogic or Nortel switch is not permitted with user ID and password . . . . The Hardware Log task is not available . . . Incorrect events reported for NICs that have a teaming configuration of active-standby . . . LED Status column is unavailable in Navigate Resources . . . . . . . . . . . . . LED Status column does not report hardware problems . . . . . . . . . . . . . . Out-of-band events are not configured correctly Out-of-band tasks fail on IPMI managed systems . . . . . . . . . . . . . . Power tasks vary by the resource. . . . . . Predictive Failure Analysis events not reported for System x3755 M3 servers . . . . . . . Switch access state remains Partial Access after access request . . . . . . . . . . . . The System Identification menu options are not available . . . . . . . . . . . . . . Configuration manager template troubleshooting. . . . . . . . . . . . Network management troubleshooting . . . . . Cannot view configuration of some switches Cannot view network interface cards . . . . Clicking pie chart on Network Management summary page may not display correct view . . IBM Systems Director Server sends unwanted or unexpected multicast packets . . . . . . . Delay in threshold page reflecting exceeded threshold . . . . . . . . . . . . . . Duplicate network monitor thresholds . . . . Offline network interface card reports incorrect status . . . . . . . . . . . . . . . IBM Power Systems management . . . . . . Using IBM i resources with an IBM Systems Director Server . . . . . . . . . . . . Remote access troubleshooting . . . . . . . File transfer hangs after management server restart on IBM System x systems . . . . . .
143 144
144 145 145 145 146 146 146 147 148 149 149 150 151 151 152 153 154 154 155 156 157 160 160 161 161 162 163 163 164 164 164 166 166
Remote command line does not work on a Windows 2003 Platform Agent managed system when invoked as launch in context . . . . . File transfer does not display files with Chinese characters in the file name if these files were transferred with a tool other than IBM Systems Director File transfer . . . . . . . . . . An error is displayed when changing the encoding of a file . . . . . . . . . . . File transfer does not support certain characters in file names when using the rename function . File transfer does not filter target file system properly . . . . . . . . . . . . . . File transfer cannot open a file that contains unprintable characters . . . . . . . . . File transfer window sometimes hangs . . . . Remote command line prompt on a Windows 2003 Common Agent managed system does not have working scroll bars . . . . . . . . System z management . . . . . . . . . . Access state is Unknown for z/VM host operating system . . . . . . . . . . . . . . Discovery of z/VM managed resources does not function correctly . . . . . . . . . . . Incorrect values are displayed for CPU Utilization and Process Count on Linux on System z . . . . . . . . . . . . . . Job status for inventory collection on IBM z/VM Manageability Access Point Agent is Complete with Errors . . . . . . . . . . . . . Network adapter status for the Linux on System z is Unconfigured . . . . . . . . Storage systems management troubleshooting . . Cannot start an IBM DS Storage Manager with version later than 10.6.x.x . . . . . . . . Could not install or uninstall on a Microsoft Windows system . . . . . . . . . . . Could not install or uninstall on a Linux or AIX system . . . . . . . . . . . . . . Cannot access PlatformAgentSubagent SMI-S for IBM SAS RAID Controller Module . . . . . DS 3000/4000/5000 proxy provider configuration causes provider to fail. . . . . Unable to discover an SMI-S provider . . . . After requesting access to an SMI-S provider, no storage systems or switches are displayed . . . SMI-S provider configuration fails to add a storage device . . . . . . . . . . . . SMI-S provider configuration fails to remove a storage device . . . . . . . . . . . . Installing the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module on additional systems completes with errors . . . Storage events not being displayed in the event log . . . . . . . . . . . . . . . . Unable to display a topology map of a SAN . . The SAN configuration profile is not updated when a blade changed in an IBM BladeCentersystem . . . . . . . . . .
167
167 167 168 168 168 169
169 169 169 170
174
175 175 176 176 176 177 178 179 179 180 180 181
182 182 183
183
vi
Replace and remap task fails with an IBM BladeCenter S SAS RAID Controller Module for a blade whose host name is more than twelve characters in length . . . . . . . . . . iSCSI configuration accepts incomplete IPV4 format addresses . . . . . . . . . . . Deploy of a SAS Zone configuration failed on an IBM BladeCenter after access to the Advanced Management Module . . . . . . No predefined SAS zone configuration when there is only one SAS switch, and it is on I/O Module 4 on an IBM BladeCenter S system . . Mismatched configuration of two SAS switches on an IBM BladeCenter S system . . . . . . Cannot view available storages when creating a logical volume in offline mode . . . . . . Cannot get some properties of storage devices SAS Port panel launched from SAS switch is not correct. . . . . . . . . . . . . . . IBM BladeCenter S SAS RAID Controller Module menu tasks are not displayed for an attached storage array (storage subsystem) . . IBM BladeCenter S SAS RAID Controller Module menu tasks fail for an attached storage array (storage subsystem) . . . . . . . . A previously supported IBM BladeCenter S SAS RAID Controller Module is no longer supported after installing IBM Systems Director 6.1.1. . . Cannot create RAID 0 level pools on certain LSI IRC devices . . . . . . . . . . . . . Capacity information is not correct for storage devices . . . . . . . . . . . . . . When managing an Integrated RAID Controller (IRC), incorrect controller device information is displayed. . . . . . . . . . . . . . Some menu options are missing for an Integrated RAID Controller (IRC) device . . . Some ServeRAID MR controller devices not supported by IBM Systems Director 6.1.1 . . . Remote Supervisor Adaptor and Remote Supervisor Adaptor-II devices not supported by IBM Systems Director 6.1.1 . . . . . . . . Storage panel or Long Running Tasks panel fails when managing ServeRAIDMR Controller or Integrated RAID Controller (IRC) devices . . . A pool with a RAID level of RAID10 on a ServeRAID MR Controller device can have a maximum of four drives. . . . . . . . . Using tasks available on Storage panel for Integrated RAID Controller (IRC) devices results in errors . . . . . . . . . . . . . . Controller error when starting a task . . . . System status and health . . . . . . . . . Automation command does not show the interactive program window . . . . . . . Cannot add selected resources to a monitor view . . . . . . . . . . . . . . . Error is encountered while loading shared libraries . . . . . . . . . . . . . .
184 184
185
185 186 186 187 187
188
188
189 189 189
190 190 190
191
192
192
192 193 194 194 194 195
Power Systems server IVM events appear in the event log with incomplete Event Text and Source fields . . . . . . . . . . . . Events are not created immediately when a threshold is exceeded. . . . . . . . . . Incorrect events reported for NICs that have a teaming configuration of active-standby . . . Monitored memory values are too high . . . Monitored disk space values are too low . . . Monitoring tasks are not displayed in the Actions menu . . . . . . . . . . . . Monitors are not listed for the selected resource No data available error for AIX and VIOS monitors . . . . . . . . . . . . . . Predictive Failure Analysis events not reported for System x3755 M3 servers . . . . . . . Resource is not returned by the browse function Resources are encountering problems that you need to monitor and manage . . . . . . . Save changes confirmation window is invoked despite no changes . . . . . . . . . . Two microprocessor monitor resources are displayed when only one microprocessor exists . Update manager troubleshooting . . . . . . . Unable to import updates from network mounted directories . . . . . . . . . . Update installation tasks never complete . . . Getting Started wizard for update manager indicates that some systems are not supported . A system cannot be chosen from the Getting Started, Install, or Install staging wizards . . . IBM BladeCenter Settings tab is not displayed When specifying IBM BladeCenter Settings, messages about empty fields are displayed . . When specifying IBM BladeCenter Settings, messages about incorrect syntax are displayed . Error occurred trying to start the TFTP server used for IBM BladeCenter and System x updates . . . . . . . . . . . . . . Compliance is not accurate for a system . . . Changes to a compliance policy's groups do not immediately result in issues . . . . . . . Check for updates does not display on the system's menu . . . . . . . . . . . . Check for updates obtains information on more updates than expected . . . . . . . . . Unable to find update compliance task logs . . Compliance status is not accurate for IBM BladeCenter I/O modules . . . . . . . . Update compliance is not refreshed when adding a nested group to a compliance policy . Multiple compliance policy entries result in multiple compliance issues for the same system . When a compliance check entry is added to a compliance policy for a system group, compliance issues are shown for both the operating system and the server . . . . . . Compliance issues not resolved after successful install of updates . . . . . . . . . . .
195 195 196 197 197 197 198 198 199 200 200 200 201 201 201 202 202 202 203 203 204
204 205 206 206 206 207 207 208 208
209 209
Contents
vii
Update compliance issue remains unresolved after installing Director 5.20.x agent updates on Linux systems . . . . . . . . . . . . Running out disk space during update download can cause random application errors and server startup errors . . . . . . . . Download of updates fails due to proxy server connection issues . . . . . . . . . . . Download of updates fails with an error of download size exceeded . . . . . . . . . Download or Import task fails to add an IBM System x or IBM BladeCenter update . . . . Unable to import update . . . . . . . . Install and Installation staging tasks not available for an update . . . . . . . . . Update installation staging does not transfer all members of an update group . . . . . . . IBM BladeCenter Install and Installation Staging tasks fail when using an FTP or TFTP server . . Installing out-of-band updates for IBM BladeCenter devices using SNMP fails . . . . Installing out-of-band updates for IBM BladeCenter devices using Telnet fails . . . . Install fails for IBM BladeCenter switch module updates that support both TFTP and FTP protocol, when only an FTP server is configured Installing an update takes too much time . . . Manually installed updates are not displayed as installed . . . . . . . . . . . . . . Manually uninstalled updates are displayed as still being installed . . . . . . . . . . Install fails when using system groups or update groups . . . . . . . . . . . . Updates from an update group have not been installed . . . . . . . . . . . . . . Scheduled Install or installation staging task fails with a connection error . . . . . . . Path length is limited to 64 characters when updating IBM BladeCenter Out of Band components . . . . . . . . . . . . . Staging of updates to TFTP server can fail on extremely slow networks . . . . . . . . Custom criteria chooser shows incorrect or missing update types for the Version category of IBM Systems Director . . . . . . . . . Updating IBM Director Agent version 5.20.1 on operating systems other than Microsoft Windows fails . . . . . . . . . . . . AIX upgrades that skip a Technology Level may not report correct new level . . . . . . .
210
211 211 212 213 214 214 215 215 216 217
218 219 220 220 220 221 222
222 223
223
Best practices for working with updates for IBM i. . . . . . . . . . . . . . . . . Uninstall fails because a restart of an IBM i system is required . . . . . . . . . . . Show installed updates and Show needed updates tasks do not display all updates . . . Virtualization manager troubleshooting. . . . . Virtualization environment troubleshooting . . Power Systems environment troubleshooting VMware VirtualCenter environment troubleshooting. . . . . . . . . . . . Xen virtualization troubleshooting . . . . . Commands troubleshooting . . . . . . . . Help and error messages for the smcli command display only in English . . . . . Unable to display man pages on SUSE Linux Enterprise Server 9.x . . . . . . . . . . Unable to run a specific smcli command . . . Unable to run smcli commands from a directory other than install_root/bin . . . . . . . . Unable to run a dircli command . . . . . . Disksize not valid error when using command line . . . . . . . . . . . . . . . . Unable to change the language (locale) . . . . Unable to use double-byte character set languages in AIX . . . . . . . . . . . Output is empty for system and inventory commands . . . . . . . . . . . . . Unable to connect to the CLI daemon . . . . genevent command troubleshooting . . . . . Storage commands troubleshooting . . . . . Update commands troubleshooting . . . . . Console logging and tracing . . . . . . . . Sensor logs and debugging . . . . . . . . . Activating a log file using a configuration file Activating logging by creating an empty log file Sensor logs for debugging . . . . . . . . Getting help and support . . . . . . . . . Finding information about IBM Systems Director problems . . . . . . . . . . . Information to provide to the IBM Technical Support Center or IBM Systems Director customer forum . . . . . . . . . . . Getting fixes. . . . . . . . . . . . . Service and support information . . . . . . IBM Systems Director Web interface messages . .
225 227 227 228 228 236 244 250 257 257 257 258 259 259 259 262 263 264 264 265 267 271 272 272 272 274 274 276 276
277 280 280 280
224 225
Notices . . . . . . . . . . . . . . 283
Trademarks . . . . . . . . . . . . . . 284
viii
About this publication

This publication provides information about specific IBM Systems Director problems and how to solve them. This book also provides strategies for troubleshooting common problems in IBM Systems Director implementations.
Conventions and terminology

These notices are designed to highlight key information: Note: These notices provide important tips, guidance, or advice. Important: These notices provide information or advice that might help you avoid inconvenient or difficult situations. Attention: These notices indicate possible damage to programs, devices, or data. An attention notice appears before the instruction or situation in which damage can occur.
Publications and related information

You can view the same content in the IBM Systems Director Information Center as PDF documents. To view a PDF file, you need Adobe Acrobat Reader, which can be downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.
Information centers and topic collections

v IBM Systems http://publib.boulder.ibm.com/eserver/ View the IBM Systems information center landing page, which provides integrated information for multiple IBM Systems products. v IBM Systems Director http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp Updated periodically, the IBM Systems Director topic collection contains the most up-to-date documentation available for IBM Systems Director. v IBM Systems Director plug-ins publib.boulder.ibm.com/infocenter/systems/index.jsp View the IBM Systems information center for information about how to install and use plug-ins that extend the functionality of IBM Systems Director. v IBM Systems Director Upward Integration Modules (UIMs) publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html Read the IBM Systems Director Upward Integration Modules (UIM) topic collection to learn about how to install and use upward integration modules and management packs that enable non-IBM workgroup and enterprise-management products to interpret and display data that is provided by Common Agent and Platform Agent. v IBM Systems Director API Licensing http://www.ibm.com/vrm/4api1
ix
View the license information regarding use of IBM Systems Director APIs and their associated documentation. Fill out the form to request API access. After your information is reviewed, you will be contacted with additional information regarding access to and use of the APIs.
Publications
APAR Readme 6.2.0 Provides information about APARs fixed in IBM Systems Director version 6.2.0. Release Notes 6.2.0 and Release Notes 6.2.1 Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software. Hardware and Software Support Guide Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software. Planning, Installation, and Configuration Guide for AIX Provides detailed instructions to install and configure each component of IBM Systems Director on system running AIX using the standard installation option. Planning, Installation, and Configuration Guide for IBM i Provides detailed instructions to install and configure each component of IBM Systems Director on system running IBM i using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on Power Systems Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for Power Systems using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on x86 Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System x using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on System z Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System z using the Standard installation option. Planning, Installation, and Configuration Guide for Windows Provides detailed instructions to install and configure each component of IBM Systems Director on system running Windows using the Standard installation option. Systems Management Guide Provides detailed instructions for using the Web interface and managing systems and resources in your environment. Troubleshooting Guide Provides information about problems and how to solve them, and strategies for troubleshooting common problems.
Events Reference Provides information about IBM Systems Director events, including the event type, description, severity, and extended details. Commands Reference Provides detailed information about the systems management command-line interface (smcli) commands, and other commands that can be run directly from the command line, including configuring the database, and starting and stopping IBM Systems Director. Hardware Command Line User's Guide Provides information about installing and using the Hardware Command Line (formerly known as the IBM Management Processor Command-Line Interface). Command output in this release might vary from command output in previous releases.
White papers and briefs

v IBM Systems Director ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/ XBW03006USEN.PDF This paper provides a detailed overview of the changes in IBM Systems Director V6.1, including the new Web interface, security features, operating system agents, integrated plug-ins and additional plug-ins that can be separately installed. v Value Proposition for IBM Systems Director ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/ XBW03007USEN.PDF This paper describes the challenges of operational management for enterprise server installations and the value provided IBM Systems Director. v Managing IBM Power Servers with IBM Systems Director 6.1 www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN &attachment=POW03011USEN.PDF Provides information about managing the virtualization and consolidation on Power systems using IBM Systems Director. v IBM Systems Director 6.1 Migration Tips www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN &attachment=XBW03009USEN.PDF Provides information about migrating data when upgrading your environment from IBM Director V5.20 to IBM Systems Director V6.1. v Performance Tuning and Scaling Guide for IBM Systems Director 6.2 http://www-01.ibm.com/support/ docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&aid=1 Provides information about how to plan, implement, configure, and use an IBM Systems Director Server to manage a large configuration with optimal performance. The Performance Tuning and Scaling Guide also contains information about the following topics: Running IBM Systems Director plug-ins, such as IBM Systems Director Active Energy Manager and IBM Scalable Systems Manager Integration with Tivoli products Implementing High Availability (HA)
xi
IBM Redbooks publications

www.ibm.com/redbooks/ You can also search this Web page for documents that focus on IBM Systems Director and specific IBM hardware; such documents often contain systems-management material. The following book is available for IBM Systems Director V6.1: Implementing IBM Systems Director 6.1 Tip: Be sure to note the date of publication and to determine the version of IBM Systems Director software to which the Redbooks publication refers.
Further information
Also see the following resources for further information about IBM Systems Director: v For alerts, discussions, news, parts and product information, and specific troubleshooting workarounds for IBM Systems Director, see the Support & downloads Web site at http://www.ibm.com/support/us/en/. Tip: To locate the information that you need, enter Systems Director in the Search field and click Search. You can then narrow your results by document type or product category, or use additional search terms. v For white papers, technotes, tips, and other documents related to IBM Systems Director, see the Techdocs Web site at http://w3.ibm.com/support/techdocs/ atsmastr.nsf/Web/Techdocs. Tip: To locate the information that you need, either select the categories that you want to search or select UNMARKED to search all categories. Then enter Systems Director in the for: field and click Search. v For solutions to all types of situations that other customers have encountered, see the IBM Systems Director customer forum at www.ibm.com/ developerworks/forums/forum.jspa?forumID=759.
Web resources
Listed here are the Web sites and information center topics that relate to IBM Systems Director.
Web sites
v IBM Systems Director www.ibm.com/systems/management/director/ View the IBM Systems Director Web site on ibm.com which provides links to downloads and documentation for all currently supported versions of IBM Systems Director. v IBM Systems Director Downloads www.ibm.com/systems/management/director/downloads/ View the IBM Systems Director Downloads Web site on ibm.com which provides links to download code IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules. v IBM Systems Director Documentation and Resources www.ibm.com/systems/management/director/resources/
xii
View the IBM Systems Director Documentation and Resources Web site on ibm.com which provides links to product documentation, redbooks, redpapers, white papers, and learning modules related to IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules. v IBM Systems Director Upward Integration www.ibm.com/systems/management/director/upward/ View the IBM Systems Director Upward Integration Web site on ibm.com which provides more information about IBM Systems Director upward integration modules created by IBM and other companies. IBM Systems Director UIMs enable third-party workgroup and enterprise systems-management products to interpret and display data that is provided by IBM Systems Director Platform Agent managed system. v IBM Systems Director Best Practices Wiki www.ibm.com/developerworks/wikis/display/WikiPtype/ IBM+Systems+Director+Best+Practices+Wiki View updated documentation and best practices for IBM Systems Director on various systems. v IBM Servers www.ibm.com/servers/ View the IBM Servers Web site to learn about IBM Systems server and storage products. v IBM ServerProven www.ibm.com/servers/eserver/serverproven/compat/us/ View the IBM ServerProven Web site to learn about hardware compatibility of IBM System x and BladeCenter systems with IBM applications and middleware, including IBM Systems Director.
Forums
v IBM Systems Director www.ibm.com/developerworks/forums/forum.jspa?forumID=759 View the IBM Systems Director forum Web site on ibm.com to discuss product-related issues pertaining to IBM Systems Director, IBM Systems Director UIMs, and IBM Systems Director extensions. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. v IBM Systems Director SDK www.ibm.com/developerworks/forums/dw_esforums.jspa View the IBM Systems Director SDK forum Web site to discuss issues pertaining to the IBM Systems Director Software Development Kit (SDK). This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. v IBM Systems www.ibm.com/developerworks/forums/dw_esforums.jsp View the IBM Systems forums Web site on ibm.com to learn about various forums that are available to discuss technology-related and product-related issues pertaining to IBM Systems hardware and software products. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information.
xiii
If you have any comments about this book or any other IBM Systems Director publication, go to the IBM Systems Director information center Web site at http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp. There you will find the feedback page where you can enter and submit comments.
xiv
Troubleshooting and support

Use this section to troubleshoot and resolve problems with IBM Systems Director 6.2 or later. To troubleshoot problems that are specific to earlier versions of IBM Systems Director, see the documentation for that version. If you run into a problem that is not covered in this documentation, check any of the following resources for further information about troubleshooting IBM Systems Director: v For alerts, discussions, news, parts and product information, and specific troubleshooting workarounds for IBM Systems Director, see the Support & downloads Web site at http://www.ibm.com/support/us/en/. Tip: To locate the information that you need, enter Systems Director in the Search field and click Search. You can then narrow your results by document type or product category, or use additional search terms. v For white papers, technotes, tips, and other documents related to IBM Systems Director, see the Techdocs Web site at http://w3.ibm.com/support/techdocs/ atsmastr.nsf/Web/Techdocs. Tip: To locate the information that you need, either select the categories that you want to search or select UNMARKED to search all categories. Then enter Systems Director in the for: field and click Search. v For solutions to all types of situations that other customers have encountered, see the IBM Systems Director customer forum at www.ibm.com/ developerworks/forums/forum.jspa?forumID=759.
Limitations and workarounds

The following topics describe limitations and workarounds for IBM Systems Director.
Discovery profile auto-unlock and auto-inventory not supported for IBM Director Agent
This problem affects users when using a discovery profile to discover IBM Director Agents.
Problem
When using a discovery profile to discover IBM Director Agents, automatically requesting access and automatically collecting inventory are not supported. Note: In the Discovery Profile wizard, the protocol for discovering IBM Director Agents is called IBM Systems Director 5.x Common Agent Discovery. The default profile that discovers IBM Director Agents is called Default Common Agent Discovery. This limitation is restricted only to IBM Director Agents supported on IBM Director 5.10 and its update versions and IBM Director 5.20 and its update versions. It does not apply to Platform Agents. When discovering a combination of
agent types with the same profile, other agents that are discovered (not IBM Director Agents) support automatically requesting access and automatically collecting inventory.
Resolution
This is a current limitation of IBM Systems Director 6.x.
Agent installation does not generate events

This problem affects installation of all agent packages on managed systems using the Agent Installation Wizard.
Problem
When you attempt to install an agent package on a managed system, no events are generated or logged.
Resolution
This is a current limitation of IBM Systems Director 6.1.
BladeCenter is offline after the AMM failed over

If Advanced Failover is configures on the Advanced Management Module (AMM), the Swap Management Module IP Addresses option must be selected. If this is not set correctly, IBM Systems Director will see the BladeCenter chassis as offline when the AMM fails over.
Changes to the network interface card (NIC) configuration cannot be deployed to operating system resources
This problem affects the Network Configuration template when applied to operating system resources.
Problem
When you try to modify the IP address, gateway, and subnet mask of the network interface card (NIC) that is currently used to interconnect on this template at the same time and want to deploy this change to the operating system resource, this task fails.
Explanation
This is a limitation of IBM Systems Director 6.1. The Platform Agent and Common Agent cannot support modification of the IP address, gateway, and subnet mask of the network interface card (NIC) used to interconnect.
Command fails on smcli

This problem affects systems running some language-specific versions of Microsoft Windows, such as Korean and Japanese versions.
Problem
When you run a command that includes a backslash (\) on the IBM Systems Director command-line interface (smcli), the command fails to run.
IBM Systems Director command-line interface (smcli) and virtualization manager commands use the backslash (\) for various commands. For example, the backslash is used when designating the full path name to a virtual server configuration file. However, some language-specific versions of Microsoft Windows use a different character for backslash. Therefore, when a backslash is used with smcli, it fails to run on that language-specific version of Microsoft Windows. For example, this problem occurs with the Korean and Japanese versions of Windows.
Resolution
No action is suggested. This problem is a known limitation.
Date and time remain editable after deselecting the Power On Server
This limitation applies to the power configuration template for RSA.
Problem
When creating a power configuration template for RSA, if you deselect Power On Server, the date and time under Power On Server will be greyed out, but will remain editable.
Delete operations take a long time to complete

This problem affects the responsiveness of IBM Systems Director Server.
Problem
When deleting a managed resource or any other resource from IBM Systems Director Server, the resource might be removed from the IBM Systems Director Web interface promptly, but IBM Systems Director Server might seem slow afterwards. Similar behavior might be exhibited when running the cleanupd command.
Investigation
A managed resource might have many other resources associated with it that must be removed along with managed resource. Processing is required to determine what other resources and relationships must be removed and this processing takes time. All of the affected resources are deleted at the same time as one transaction in the database. The database transaction might be a long-running process that consumes a lot of processor bandwidth. IBM Systems Director can be configured to use one of four databases: Apache Derby, IBM DB2 Universal Database, Microsoft SQL Server, and Oracle Database. IBM DB2 Universal Database, Microsoft SQL Server, and Oracle Database all perform these deletions faster than Apache Derby, sometimes four or five times faster. The deletion will complete successfully after the required processing time and IBM Systems Director Server will return to its normal state.
Resolution
To workaround this limitation, schedule these problematic delete operations during times when the least number of users will be affected.
Error messages include placeholder text

This limitation affects error messages displayed in the IBM Systems Director Web interface.
Problem
Some error messages that are displayed in the IBM Systems Director Web interface might contain dynamic data. If you click the error message identifier to view detailed information, placeholder text is displayed in the error message instead of the dynamic data.
Resolution
This is a limitation of IBM Systems Director 6.1. To view the error message with the dynamic data, return to the original error message.
Completion status for the Send a numeric page event action is incorrect
(IBM Systems Director 6.1 only) This problem affects the Send a numeric page event action. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
After the Send a numeric page event action has been invoked, its action history reports that the Launch Status for the event action is Failed but that the Completion Status for the event action is Not completed yet.
Resolution
Excessive windows prompting for undoable disk power actions

This problem affects systems using virtualization manager subagent for VMware VirtualCenter.
Problem
When a virtual server has one or more undoable disks and a power operation occurs on that virtual server, VMware VirtualCenter requires user input to complete the operation. If the power operation is originated by IBM Systems Director, then IBM Systems Director provides the required input. However, if there is a VMware Remote Console open at the time that the power operation occurs, a window opens that asks for the required information even though it has been provided by IBM Systems Director. When a user attempts to provide the information that was requested, an error message is displayed.
Resolution
File Manager displays a blank table

This problem affects Common Agent managed systems.
Problem
You are using IBM Systems Director and select System Configuration > Remote Access > File Management on a Common Agent or Level 2: IBM Director Agent version 5.20 managed system. You navigate to a directory with more than 16,000 files in it and a blank table appears after a few minutes.
Explanation
When using Common Agent or Level 2: IBM Director Agent version 5.20, the number of files under a directory that File Manager can return is less than 16,000 files. If the number of files under a directory is more than 16,000 the File Manager table appears blank.
Resolution
If you are using Common Agent or Level 2: IBM Director Agent version 5.20, only select directories with less than 16,000 files in File Management.
File Manager fails to copy files larger than 1.5 GB

This problem affects Microsoft Windows managed systems.
Problem
You are using IBM Systems Director to discover a Windows managed system and have gained full access to the target system. You right-click the operating system for the target system and select System Configuration > Remote Access > File Management. Then you upload a file greater than 1.5 GB. The upload command fails.
Explanation
This problem is related to the available memory on the server. File Manager needs a server to have a large amount of available memory to load a big file. If the server does not have enough memory, it will not be able to upload a big file to transfer.
Resolution
To correct this problem, increase the memory on the server, or stop other applications to increase the amount of available memory.
Help selection is a question mark

This problem affects the IBM Systems Director Web interface in Italian only.
Problem
For Web browsers that are set to Italian, the Help selection provided in the upper right corner of the IBM Systems Director Web interface is represented by a question mark (?).
Resolution
This is a limitation of IBM Systems Director 6.1. Click ? and the help topic is displayed correctly.
IBM Storage Configuration Manager (SCM) 2.10 or earlier does not support non-English operating systems
This problem affects users of IBM Storage Configuration Manager version 2.10 or earlier.
Problem
IBM Storage Configuration Manager (SCM) version 2.10 or earlier does not have National Language Support built-in. As a result, it is not supported to run on non-English operating systems.
Resolution
This is a current limitation of IBM Storage Configuration Manager 2.10 or earlier versions.
Limitations using IBM Systems Director to manage resources behind a NAT firewall
This problem affects users who attempt to use IBM Systems Director to manage any one of several types of resources that is located behind a network address translation (NAT) firewall.
Problem
IBM Systems Director cannot manage a Remote Supervisor Adapter, a Remote Supervisor Adapter II, or a Management Module that is located behind a NAT firewall. Also, a few other types of resources that are located behind a NAT firewall might be unable to reliably send events to the management server.
Explanation
The following limitations affect IBM Systems Director when attempting to manage resources that is located behind a NAT firewall: v A Remote Supervisor Adapter, a Remote Supervisor Adapter II, or a Management Module that is located behind a NAT firewall cannot reliably respond to SLP requests received from Systems Director. The device receives the SLP request on port 427 but sends a response on a random port number, which NAT does not support. This inability to reliably communicate with the management server prevents Systems Director from discovering the device. v When located behind a NAT firewall, a few types of resources cannot reliably send events to the management server. Resources that are negatively affected by being located behind the NAT firewall include a Platform Agent managed system, an Advanced Management Module, and a Hardware Management Console. Important: Systems Director can successfully discover and manage a properly configured Common Agent managed systems. For more information about configuring a Common Agent managed system, see the Common Agent installation instructions for the platform on which the agent is installed.
Resolution
The preceding problems are known limitations for Systems Director 6.1.2.
Capacity information is not correct for storage devices

The capacity information displayed on the Local Storage row of the Storage Management Summary page is not correct.
Problem
The Local Storage row on the Storage Management Summary page is not correct. The raw capacity, available capacity, and usable capacity show a default value of 0 because of this limitation. The other rows (Network storage and IBM BladeCenter storage) are correct.
Resolution
Use operating system utilities or storage management applications to determine usable and available storage capacity.
JAWS screen reader does not indicate that an update has taken place
When viewing the Storage Resources information with the JAWS screen reader, there is no indication that an update has been made to the display.
Problem
Using the JAWS screen reader, select a server from the Resource Navigator and click Actions > System Configuration > Storage Resources. From the Storage Frame, go to the Configurations link. Click Refresh from any link, such as: Configurations, Storage pools, disk drives, and so forth. When the page is refreshed, JAWS does not indicate that an update has been done. So, the user is not notified that an update has been applied.
Multi-Switch Interconnect Module (MSIM) vital product data is missing from inventory
(IBM Systems Director 6.1 only) This problem affects Multi-Switch Interconnect Module (MSIM) resources only. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
The vital product data (VPD) for Multi-Switch Interconnect Modules (MSIMs) is not available in the inventory collection for the BladeCenter chassis. MSIM vital product data can include part numbers and field-replaceable unit (FRU) numbers.
Explanation
This is a limitation of IBM Systems Director 6.1.
Table view entries do not include Linux operating system version information
This problem affects Common Agent managed systems and Platform Agent managed systems that run the Linux operating system.
Problem
After discovering and requesting access to Common Agent managed systems or Platform Agent managed systems that run the Linux operating system, discovery results and other table views do not display the Linux version information for these systems. Affected table views include the discovery results (the Discovered Manageable Systems table) and the tables displayed by using the Navigate Resources task.
Resolution
To resolve this problem, collect inventory for the affected systems. After collecting inventory, table view entries for the affected systems include the Linux operating system version information.
Event Filter Builder tree displays multiple Windows event log nodes
This problem affects the Event Filter Builder tree in the advanced event filter path of the Event Automation Plan wizard.
Problem
In the Event Filter Builder window (a Launched task provided for advanced event filter creation), on the Event Type page, when you clear the Any check box, two selection nodes are displayed for Windows Event Log events: v CIM > Windows NT Event Log v Windows Event Log
Resolution
IBM Systems Director 6.1 is working as designed. You can create an event filter with either selection.
The OID for different SNMP traps are the same

This problem affects the Send an SNMP trap reliably to a NetView host event action.
Problem
For any event that the Send an SNMP trap reliably to a NetView host event action redirects as a trap to a NetView console, the trap has the same OID.
Explanation
This is a limitation of IBM Systems Director 6.1 as well as IBM Director version 5.20 and earlier.
Removing a managed operating system does not remove the managed server
This limitation affects removing a managed system from management by IBM Systems Director.
Problem
Managed systems are represented by two resources in IBM Systems Director: a server resource that represents the physical server, and a system resource that represents the operating system installed on the server. When you remove a system resource, the corresponding server resource for the managed system is not removed.
Explanation
This is a known issue with IBM Systems Director.
Resolution
v After removing the system resource, also remove the corresponding server resource.
Limitations of large tables

These problems exist in the table views in the IBM Systems Director Web interface.
Problem
1. When you select a group that contains related resources, the resources are normally displayed as nested resources in a table. However, when the group contains a large number of discovered resources, you notice that the resources are not displayed in a nested view. For example, you might see a list of virtual servers that are not indented under their associated hosts. In addition, the following message is displayed at the top of the interface:
X items are in the group. Y have been filtered and are displayed.
where X is the number of resources contained in the group, and Y is the number of resources that have been filtered and are displayed in the table. 2. When the selected group contains a large number of discovered resources, searching and filtering may not be available for some columns. Specifically, columns for which values can contain a list of items may not support search and filtering. Columns that cannot be filtered will not have a filter link when the filter row is displayed. Columns that cannot be filtered will also not support the search function. For example, searching on the contents of the IP Addresses or IP Hosts columns in large tables does not work.
Explanation
These problems can occur when the total number of resources and relationships in a group exceeds 1,000. These problems are a known limitation of the table view.
Selections or data entered into fields is lost

This problem affects any IBM Systems Director pages and windows that contain lists, check boxes, radio buttons, and text entry fields.
Problem
If you make a selection or enter data in a field, then click on another page which overlays the first page, and then return to the first page, the selections and data that you entered on the first page are lost. Selections made using lists, check boxes, or radio buttons are also affected.
Explanation
The form-persistence capability is not enabled. This is a limitation of the current release.
Severe log entry in the trace log

This problem affects IBM Systems Director Server when the IBM BladeCenter and System x management plug-in is installed.
Problem
After stopping IBM Systems Director Server, the IBM BladeCenter and System x management Welcome page plug-in logs the following severe log entry in the trace log: SEVERE The bundle context is null ::class.method=ModularWelcomeBundleActivator.removedService () ::thread=Thread-1 ::loggername=com.ibm.sysmgt.welcomepage.modular
Resolution
This is a limitation of IBM Systems Director 6.1. You can ignore this log entry.
The Severity column always reports Information

This problem affects the Hardware Log task when used on a resource that contains an IPMI Baseboard Management Controller (BMC) service processor.
Problem
When viewing hardware log entries retrieved from a BMC service processor, the severity is always reported as Information.
Explanation
This is a limitation of the BMC service processor. Log entries in the BMC service processor do not contain severity information. The Hardware Log task displays Information as a default value.
Warning message recorded after installing the SMbus or LM78 device driver
This problem only affects systems running Red Hat Enterprise Linux.
Problem
If you install the IBM SMbus or LM78 device driver, a warning message similar to the following message might be recorded in the Bootmsg.log file: depmod: *** Unresolved symbols in /lib/modules/2.4.7-10smp/kernel/drivers/ char/driver.o where driver is either ibmsmb or ibmlm78.
10
Explanation
This warning message is generated if the Red Hat Enterprise Linux kernel was compiled with versioned symbols enabled. Ignore this message; the device driver loaded and will operate correctly.
Switch does not respond to IP address change

(IBM Systems Director 6.1 only) This problem affects IBM BladeCenter switches that are not discovered by way of the BladeCenter chassis. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
When a switch is directly discovered and not discovered through the BladeCenter chassis, the switch does not response to an IP change. If you discover a switch, change the switch IP address and then discover the switch again with the new IP address, a second switch managed resource is created. The first managed resource displays Offline after 15 minutes.
Resolution
If you need to change the IP address for the switch that was discovered directly, complete the following steps to workaround this problem: 1. Before you change the IP address, delete the switch managed resource in either of the following ways:
From the command line: smcli rmsys -n system_name where system_name is the unique ID or name of the system. Right-click the switch and click Remove.
In the IBM Systems Director Web interface
2. Change the IP address. 3. Discover the switch again.
Switch information is not accurate in IBM Systems Director Server

Switch alerts are not reflected on the switch resource in the IBM Systems Director Server.
Problem
Telnet to the switch from a command line session and issue some commands such as switchDisable or portDisable. The state change is not reflected on the switch resource in IBM Systems Director Server. The access state of the switch remains unlocked. The command switchDisable will cause all Fiber Channel ports to be offline, but the user can still configure the switch. The switch itself is still online and can be configured.
11
IBM Systems Director Server might fail to start in IPV6-only environment on Linux platform
This problem affects the IBM Systems Director Server when configured for IPv6-only after being installed on a Linux system.
Problem
After IBM Systems Director Server is installed on a Linux system that has (or is changed to) an IPV6 network configuration, one of the following problems might occur: v After a significant time, the server does not start v After starting, which might take a significant time, IBM Systems Director does not function correctly. For example, the IBM Systems Director Web interface might be unavailable. When IBM Systems Director is installed on a system with an IPv4 network configuration, you might re-configure the system to have an IPv6-only environment. After re-configuring the environment as IPv6 and restarting the server, you might encounter any of the following results: v The local operating system management resource and local server go offline. v The server fails to start. v The server starts after a significant time, but IBM Systems Director does not function correctly.
Resolution
To set up an IPv6-only environment on a Linux system, verify that the system uses the following configuration settings before you install IBM Systems Director Server or Common Agent: 1. Configure only global IPv6 addresses on all the Ethernet interfaces. IBM Systems Director 6.2.0 does not support link-local IPv6 addresses. 2. Use the hostname command to get the host name for the system. 3. Make sure that the host name returned in step 2 is mapped exclusively to the associated IPv6 address configured in step 1 by editing the /etc/hosts file. Verify that the /etc/hosts file contains only IPv6 addresses. For example, if the host name is server.abc.com, the contents of /etc/hosts might look like the following example:
::1 2002:1234:5678::1 # 10.12.34.56 localhost, localhost.localdomain server.abc.com server.abc.com
Note: Comment out or remove the original IPv4 addresses, with the following exception: 127.0.0.1. Even when configured as IPv6-only, the 127.0.0.1 IPv4 loopback address is still reachable, so using 127.0.0.1 is optional. Some Linux distributions use a default value of localhost6 for the ::1 IPv6 loopback address, which is different from localhost for an IPv4 configuration. In this case, keep 127.0.0.1 as the localhost value. 4. Configure a reachable DNS server with IPv6 address in the /etc/resolv.conf file. This entry is used for IBM Systems Director Server and Common Agent to resolve other host names to the correct IPv6 addresses. v Because the system is IPv6-only, the DNS server must have an IPv6 access channel. Any IPv4 address is regarded as not reachable.
12
v If the DNS server returns an IPv4 address for a host name, the IPv6-only IBM Systems Director Server or Common Agent is unable to connect to the IPv4 address. A possible workaround for this issue is to add the same entries from the DNS server to the /etc/hosts file so that they resolve to IPv6 addresses. The Linux system first uses the /etc/hosts file, then uses the DNS server. Having IPv6 entries in the /etc/hosts file ensures that the host names resolve to correct IPv6 addresses.
Tables are not displayed correctly

This problem affects the IBM Systems Director Web interface on all platforms.
Problem
When changing between pages by clicking on the tabs in the IBM Systems Director Web interface, tables displayed on the page might not be displayed correctly.
Resolution
This is a limitation of IBM Systems Director 6.1. Click on the tab again and the page will redraw and the tables will be displayed correctly.
The cimserver service stops

This limitation affects Platform Agent managed systems with both Platform Agent and the LSI MegaRAID provider installed when the Xen kernel is enabled.
Problem
After a Platform Agent managed system is discovered, the CIM server stops.
Explanation
This is a limitation. The LSI MegaRAID provider is not supported on systems with the Xen kernel enabled.
Unable to filter events for virtual server failures

This problem can affect systems that are running the virtualization manager subagent for Microsoft Virtual Server, VMware ESX Server, or VMware VirtualCenter.
Problem
You have created an automation plan using one of the following event filters: v Managed Resource > Managed System Resource > Logical Resource > System > Computer System > Server > Relocation > Virtual server relocation failed. v Managed Resource > Managed System Resource > Logical Resource > Service > Virtualization Service > The command did not complete successfully. v Managed Resource > Managed System Resource > Logical Resource > System > Computer System > Server > Power > The command did not complete successfully. v Managed Resource > Managed System Resource > Logical Resource > System > Computer System > Server > Lifecycle > The command did not complete successfully.
13
v Managed Resource > Managed System Resource > Logical Resource > ServiceAccessPoint > RemoteServiceAccessPoint Service > The command did not complete successfully. v Managed Resource > Managed System Resource > Logical Resource > System > Admin Domain > Farm > Lifecycle > The command did not complete successfully. v Managed Resource > Settings > Resource Allocation Settings > Changes > The command did not complete successfully. The target system for the event automation plan is a system running virtualization manager subagent for Microsoft Virtual Server, VMware ESX Server, or VMware VirtualCenter. A task such as a virtual server relocation or a virtual server power operation failed on one of the systems where the automation plan is applied, but the automation plan was not processed as expected.
Explanation
IBM Systems Director cannot filter the failed events for systems running Microsoft Virtual Server, VMware ESX Server, or VMware VirtualCenter. This problem is a current limitation.
Unable to run more than two smcli commands simultaneously

This problem affects management servers only.
Explanation
The smcli infrastructure is limited to allow only two commands to run in parallel. All subsequent commands are queued up.
User with a blank password cannot perform operations on Windows systems

This problem affects users with a blank password who attempt to perform IBM Systems Director operations on Windows systems.
Problem
A user with a blank password cannot perform IBM Systems Director operations against Windows systems.
Resolution
Virtual farm events are not filtered

This problem can affect virtual farms in any virtualization environment
Problem
You have created an automation plan with the event filter, A virtual farm has been created. You have selected to apply the automation plan to the group, Virtualization Groups. A virtual farm event occurs, but the automation plan is not processed as expected.
14
Resolution
Edit the automation plan and select the target group to be All Systems, instead of Virtualization Groups.
Virtual farm view does not refresh when hosts change

(IBM Systems Director 6.1 only) This problem can affect host information in any virtualization environment. This problem is resolved in IBM Systems Directorversion 6.1.1.
Problem
You have the Virtual Farms view open in the IBM Systems Director Web interface, and subsequently add or remove hosts from a virtual farm. However, the host information is not updated dynamically in the Virtual Farms view.
Resolution
To refresh the Virtual Farms view, close the tab, and open it again. Expand Availability in the navigation pane, and select Virtual Farms.
Virtual server becomes unusable during relocation

This problem affects systems using virtualization manager subagent for Microsoft Virtual Server and running under Microsoft Virtual Server 2005.
Problem
Sometimes Microsoft Virtual Server 2005 does not properly unregister virtual servers. When this problem occurs, a virtual server cannot be easily reregistered, which causes it to become unusable. This problem can occur during any unregister and reregister operations, but is exposed during relocation as the relocation process involves unregistering and reregistering virtual servers. This limitation does not apply to virtual servers that are running under Microsoft Virtual Server 2005 R2.
Resolution
Virtualization manager tasks fail to start in multi-NIC environment

(IBM Systems Director 6.1 only) This problem affects systems that have multiple, active network interface cards (NICs) installed, as well as IBM Systems Director virtualization manager subagent. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
When you attempt to start a virtualization manager task, such as Connect, the task does not seem to work.
Investigation
You can check the activation logs to confirm an error.
15
1. After starting the task, an information message appears at the top of the screen stating that the job has started. Click Display Properties within the message. 2. On the Active and Schedule Jobs page, click the Logs tab. Scroll down on the page to see the Activations Logs. 3. You might see an error message similar to the following message:
DNZVMK025E The operation Connect task cannot be performed for the system IBM 8863 1RU XxXxXxX. The IPC remote service access point does not have the required access state to perform the operation.
Resolution
IBM Systems Director virtualization manager subagent does not support multiple, active NICs; this is a known limitation. If you have a system with multiple active NICs, you can perform the following workaround: 1. Uninstall IBM Systems Director virtualization manager subagent and the Common Agent. 2. Disable one of the NICs. 3. Reinstall the Common Agent and IBM Systems Director virtualization manager subagent. 4. Complete the discovery process again, and attempt the virtualization manager tasks again.
Add or Remove Programs displays an incorrect program size for Platform Agent
This problem affects Platform Agent on Windows 2003 and Windows 2008.
Problem
When you navigate to Control Panel > Add or Remove Programs on Windows, Platform Agent is listed with an incorrect program size in MB.
Explanation
This is a known limitation of IBM Systems Director on Windows 2003 and Windows 2008.
Resolution
There is no resolution for this limitation. The correct size for the installed Platform Agent is approximately 45MB.
Antivirus programs might conflict with certain IBM Systems Director processes
Certain Symantec Antivirus and McAfee program functions can conflict with certain IBM Systems Director processes and cause problems in your environment.
Problem
Symantec Antivirus v10 Tamper Protection and McAfee On-Access Scan can slow down or even block some IBM Systems Director processes. If your system is having this problem, you might notice any of the following symptoms: v A notification alert is displayed saying that communication to the IBM Systems Director Server was lost.
16
v Tasks fail or hang. v Hardware monitoring fails. v Various other unknown issues arise.
Resolution
Update your system to use Common Agent 6.1.1 or later.
Additional information
See Symantec Antivirus v10 Blocks IBM Systems Director Processes or McAfee On-Access Scan May Conflict with Certain Director Processes for further information about and workarounds for these problems.
Receiving alerts associated with an LSI 1030 Controller

Only IBM Systems Director CIM events are generated for alerts associated with an LSI 1030 controller. This issue is documented in APAR IC62863.
Problem
Alerts for issues with the LSI 1030 controller are only sent as IBM Systems Director CIM events. Event though the CIM subscriptions are enabled for other handlers, such as SNMP and TEC, these event types are not generated.
Resolution
Since this is an older controller, support for additional alert types will not be added. However, IBM Systems Director can be used to forward the alerts to the needed endpoints by creating an event action plan that receives the alert and forwards it in the proper format, such as SNMP trap or TEC event, to the appropriate end point.
The Adaptec ServeRaid manager for theCommon Agent must be installed in order to receive CIM events associated with the LSI 1030 controller.
Incorrect version listed for Common Agent 6.2.0.1 on AIX

This problem affects Common Agent 6.2.0.1 on discovered AIX systems.
Problem
After discovering an AIX system that contains Common Agent 6.2.0.1, the Common Agent version that is listed in /opt/ibm/director/version.key does not match the version that is displayed on the IBM Systems Director Web interface, and both are incorrect.
Explanation
The /opt/ibm/director/version.key file is not updated for 6.2.0.1.
17
Resolution
This problem does not have any impact on the functionality of IBM Systems Director, so you can ignore it.
Cannot restart the OS for managed AIX 6 CAS

This problem affects AIX systems.
Problem
From the IBM Systems Director system, you run the shutdown -r +1 remote command to restart the AIX 6 operating system on a managed common agent services agent. However, the command hangs when unmounting the file systems and fails to restart the operating system.
Explanation
The remote command line does not have the appropriate file permissions to unmount the file systems on an AIX 6 system. This is a limitation of AIX 6.
Resolution
Complete either of the following steps to solve this problem: v Run the unmount all command on the agent system, then restart the agent. v Edit the /etc/rc.shutdown file on the agent system to add the following new line: sh unmount all
Update manager limitations and workarounds

This section describes limitations and workarounds specific to the update manager plug-in.
Compliance policies incorrectly indicate that MegaRAID controller firmware needs updating
This problem affects the update manager and Inventory tasks for Platform-Agent managed systems with MegaRAID controllers. The problem has been specifically observed for the ServeRAID-MR10k SAS/SATA controller.
Problem
This problem is described by two behaviors: v After successfully installing a firmware update for the MegaRAID controller and collecting inventory, a subsequent compliance policy for the system reports that the firmware needs to be updated. v Inventory reports only the first four characters of the firmware version level.
Explanation
This is a limitation. The provider expects the firmware version level to have only four characters, but the MegaRAID controller firmware version levels have more than four characters.
Resolution
Manually check the firmware version.
18
Cannot update Linux distribution-certified device drivers

This limitation affects the update manager task when applied to systems running Linux.
Problem
By default, IBM Systems Director cannot deploy IBM device-driver updates for Linux to systems that are using the Linux distribution-certified device drivers.
Resolution
To enable deployment and compliance checking of these systems, you must modify the XML file that is included with the IBM update. Complete the following steps: 1. Download the update that you want to use. 2. Make note of the ID for the update. 3. Edit the XML file for the update: a. Navigate to the install_root\updates\data\ directory, where install_root is the root directory of your IBM Systems Director installation. b. Open the id_name.xml file, where id_name is the ID for the update. c. For the UnattendedInstallCommandLine entry, change the --force-if-overridden value to --force. d. Save the XML file with the changes. 4. Import the update using the new XML file again. 5. Continue as before, deploying the update to the target system.
Update Manager does not support compliance policies for some devices
Update manager supports update deployment for the specified software for some devices, but does not support compliance policies for these devices.
Problem
Update manager supports update deployment for the specified software on the following devices, but does not support compliance policies: v Intel Chipset device driver v MSI Chipset device driver v OSA device driver
Explanation
This is a limitation.
Cannot set up a compliance policy for a device that does not have drivers installed
This limitation affects compliance policy feature of update manager.
Problem
IBM Systems Director cannot set up a compliance policy for a device on a managed system if there are no device drivers already installed for the device.
19
Resolution
To enable update deployment and creation of compliance policies for devices, install drivers for the devices.
Update manager does not support update deployment or compliance policies for some devices
Update manager does not support update deployment or compliance policies for the specified software on certain devices.
Problem
Update manager does not support update deployment or compliance policies for the specified software on the following devices: v AMD PowerNow device driver v Broadcom for IBM BladeCenter JS21 v cKVM firmware v IBM 10 GB Ethernet device driver v IBM 10 GB Ethernet network interface card v Intel IDE MegaRAID device driver v LSI MegaRAID firmware v Netxen 10Gb Ethernet daughter card v Remote Supervisor Adapter II video BIOS
Explanation
Update manager cannot set up compliance policies for Adaptec 8i, 8k, and 8k-l controllers
This limitation affects the update manager task for IBM Systems Director.
Problem
Attempting to set up compliance policies for Adaptec 8i, 8k, and 8k-l controllers does not succeed because the controllers are not added to the inventory.
Resolution
Add the controllers to the inventory using one of the following procedures: v Platform-Agent and Common-Agent managed systems Install the appropriate Adaptec provider, and then restart the managed system. Note: The restart is required for all systems that you update. v Agentless managed systems: Install a filter driver by manually sending the driver or firmware update package for the controller to the managed system, and then restart the managed system.
Compliance check for PCI-XDDR SAS firmware on IBM BladeCenter model JS21 does not raise compliance issues
This limitation affects update manager when working with the IBM BladeCenter model JS21.
20
Problem
Update manager will always show the PCI-XDDR SAS firmware for the IBM BladeCenter JS21 blade as compliant. Update manager will not alert the user that the firmware needs to have updates installed.
Explanation
At present, there is only one PCI-XDDR SAS firmware update available. It is unlikely that a monitored system is out of date. If needed, you can force install the update.
IBM i compliance displays installed PTF groups as required

This problem occurs when you use IBM Systems Director 6.1 to manage IBM i systems running IBM Director 5.20.x.
Problem
You have installed a group PTF for IBM i systems running IBM Director 5.20.x., but you do not see the green status in update manager that you expect. Instead you might see a yellow status for those systems.
Explanation
IBM Director 5.20.x inventory does not contain group PTF information. Without that inventory information, IBM Systems Director 6.1 will always show group PTFs as being required When a PTF group is added to the compliance policy, compliance will show a red status if group PTFs are missing. If all the individual group PTFs are installed, but the group PTF information is missing, compliance will show a yellow state. IBM Director 5.20.x systems in yellow compliance state might be fully compliant. This is a known limitation for IBM i updates.
Update installation task fails because required update is not applicable for installation
This problem affects users of update manager.
Problem
When installing updates to the IBM Systems Director management server, the installation of one or more updates fails with an error that is similar to the following example error: Note: The updates in this error message are not specific to this problem; they are provided as an example. ATKUPD760I Start processing update "com.ibm.director.hw.storage.console.feature_6.2.1" and system "564d537b-92eb-764e-65d9-9eadb8d25210". (346) ALR0285I: Updating com.ibm.director.hw.storage.console.feature from jar:file:/C:/Program Files/IBM/Director/data/updateslib/Director/ com.ibm.director.hw.storage.console.feature_6.2.1/ com.ibm.director.hw.storage.console.feature_6.2.1.zip!/site.xml
21
(1458) com.ibm.director.hw.storage.console.feature: org.eclipse.core.runtime.CoreException: Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information. Status ERROR: org.eclipse.update.core code=4 Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information. null children=[Status ERROR: org.eclipse.update.core code=4 ----- Current configuration problems ----- null children=[Status ERROR: org.eclipse.update.core code=1 System z Summary Page Feature (6.2.0) requires feature "com.ibm.usmi.kernel.persistence.feature (6.2.0)", or later version. null Status ERROR: org.eclipse.update.core code=1 System z Groups Feature (6.2.0) requires feature "com.ibm.usmi.kernel.persistence.feature (6.2.0)", or later version. null] Status ERROR: org.eclipse.update.core code=4 ----- Configuration problems after the operation ----- null children=[Status ERROR: org.eclipse.update.core code=1 System z Summary Page Feature (6.2.0) requires fea-ture"com.ibm.usmi.kernel.persistence.feature (6.2.0)", or later version. null Status ERROR: org.eclipse.update.core code=1 System z Groups Feature (6.2.0) requiresfeature "com.ibm.usmi.kernel.persistence.feature (6.2.0)", or later version. null Status ERROR: org.eclipse.update.core code=1 IBM Director Storage console feature (6.2.1) requires feature "com.ibm.director.hw.storage.server.feature (6.2.1)", or later version. null]] ATKUPD767W The installation of update "com.ibm.director.hw.storage.console.feature_6.2.1" was not successful for system "564d537b-92eb-764e-65d9-9eadb8d25210". The part of the error message that pertains to this problem is as follows: IBM Director Storage console feature (6.2.1) requires feature "com.ibm.director.hw.storage.server.feature (6.2.1)", or later version. This means that update com.ibm.director.hw.storage.console.feature_6.2.1 requires update com.ibm.director.hw.storage.server.feature to be installed with version 6.2.1 or greater, but com.ibm.director.hw.storage.server.feature _6.2.1 is not installed.
Investigation
To determine the cause of the failure, check for the following two situations: v Check to see if message ATKUPD714W is displayed in the job log. For example: ATKUPD714W The update "com.ibm.director.hw.storage.server.feature_6.2.1" is not applicable to the system "564d537b-92eb-764e-65d9-9eadb8d25210", the update will not be installed to this system.If the update that is listed in that message matches the missing required update that is listed in the installation failure message, the required update was, for some reason, not applicable after the updates were acquired. v Check for the existence of a message like the following message in the error log: 2010/06/21 18:43:06.171 SEVERE Unable to get all newly registered elements. Returning 35 of 36 ::class.method=com.ibm.usmi.services.updates.util.MesUtilities.
22
getNewlyRegisteredElements() ::thread=TaskCompletionListener-thread-1 ::loggername=com.ibm.usmi.services.updates Note: The numbers 35 and 36 are not specific to the error; they are variables in the message.
Explanation
A timing issue in IBM Systems Director 6.2.0 keeps some newly-acquired updates from running through the Update Compliance task. If the updates are not validated by compliance, they are not applicable for installation. If the updates are not installed, anything that requires them for installation will also fail to install. Note: This timing issue is typically seen on only very fast systems.
Resolution
Retry the update installation.
A fix for this problem is provided in IBM Systems Director version 6.2.0.1 and later.
Update installation task fails with error message ATKUPD826E

This problem affects users of update manager.
Problem
When using the Update IBM Systems Director page or the installneeded CLI command to import and immediately install updates, the task fails with the following error message: ATKUPD826E - Updates could not be downloaded because they were not found at the download location.
Investigation
The job log for the update installation task or the installneeded CLI command output should provide an error message with the updates that were not downloaded. For example:
ATKUPD611E The update "com.ibm.director.mgr.remote.server.feature_6.2.1" has not been downloaded, so it will not be staged or installed. Download the update, and attempt to perform the operation again.
Check to see if the update is listed as downloaded by running the smcli lsupd -al updateid command. For example:
c:\download\server\SysDir6_2_1>smcli lsupd -al com.ibm.director.mgr.remote.serve r.feature_6.2.1 com.ibm.director.mgr.remote.server.feature_6.2.1: DisplayName: IBM Systems Director remote manager server feature Description: Provides the IBM Systems Director remote manager server fun ctionality. Version: 6.2.1 UpdateID: com.ibm.director.mgr.remote.server.feature_6.2.1 Severity: Medium ComponentName: IBM Systems Director Vendor: IBM Corporation RestartType: Restart after all updates are installed Superseded: false
23
Platform: Director Uninstallable: false BuildDate: 2010-08-25T00:52:02-04:00 BuildNumber: LGZU26A FixType: Individual PackageType: baseInstall SoftwareID: SystemsDirector Category: Application ImpactStatement: Availability AcquiredDate: 2010-08-27T16:11:15-04:00 TotalSize: 305148 Downloaded: yes Filenames: { com.ibm.director.mgr.remote.server.feature_6.2.1.zip, com.ibm.director.mgr.remote.server.feature_6.2.1_readme.txt, com.ibm.director.mgr.remote.server.feature_6.2.1.dd.xml, com.ibm.director.mgr.remote.server.feature_6.2.1.pd.sdd } FILES: Size Type Status Purpose Filename 284586 installable downloaded content com.ibm.director.mgr.remote.server.feature_6.2.1.zip 9885 metadata downloaded deploymentDescriptor com.ibm.director.mgr.remote.server.feature_6.2.1.dd.xml 3037 metadata downloaded packageDescriptor com.ibm.director.mgr.remote.server.feature_6.2.1.pd.sdd 7640 metadata downloaded readMe com.ibm.director.mgr.remote.server.feature_6.2.1_readme.txt
Explanation
On faster systems, there is a rare condition that can occur when immediately installing needed updates after importing them, which is accomplished by using the import path from the Update IBM Systems Director page or the -F option with the installneeded command. In this situation, updates are processing in the database on previously created records that represent updates. However, the installation code is already running on resources in memory that have not yet had their property values updated. This leads to the error about an update that is not downloaded but actually is downloaded.
Resolution
Resolve this issue based on the value of the Downloaded property: v If the value of the Downloaded property is yes, then the update is downloaded and the error is the result of a timing issue. In this case, retry the installation by running smcli installneeded -v -F -I. Because the updates are already downloaded, the installation should start and the staging step should complete successfully. v If the value of the Downloaded property is no, then ensure that all of the files are in the source import location, then run the smcli importupd command with the -o option. After the updates are downloaded, restart the installation.
To view the job log for the update installation task in the IBM Systems Director Web interface, complete the following steps: 1. Click on Navigate Resources. 2. Open the All Systems group by clicking on the link above the group name. 3. Find the server resource that represents the IBM Systems Director management server. Click the link on the system name to view its properties.
24
4. Click the Applied Activities tab. 5. Find the Install Updates job activation and click the link for it. 6. Click on the Logs tab for the Install Updates job to view the logs for the job.
Update manager task for AIX fails though operating system levels are updated correctly
This problem affects the use of update manager to update AIX .
Problem
When using update manager to install AIX updates, the installation task might occasionally fail with a status of Complete with errors. However, the AIX operating system level is successfully updated.
Explanation
The update manager for AIX extension deems an update installation successful when both of the following conditions are satisfied: v The installp command completes with a return code of zero v The oslevel -s command returns a value that matches the expected AIX level The update manager for AIX extension uses the installp command to update AIX . This process installs installp file sets in the update package. If one or more file sets are not correctly installed, the installp command fails with a nonzero return code. Update manager then considers the task not totally successful and sets the status of the task to Complete with errors. The result of the oslevel -s command returns the AIX operating system level. The command checks only certain file sets, though, and some are overlooked. So, even if the level of the AIX operating system appears to be updated when you use this method to check it, some file sets in the update package were potentially still not installed correctly.
Resolution
If the installp command returns a status of Complete with errors when you apply updates to AIX , run the oslevel -s command on the target system to see if the level value has changed and take the appropriate action depending on the results: The level value has changed If the level value has changed, then most likely the major updates were applied successfully but some packages failed to install. Packages can fail to install for many reasons, including because prerequisites are missing or the packages were not previously installed and therefore not eligible for update. Complete the following steps to solve the problem: 1. See the /var/adm/ras/nim.installp log file for details about the packages that failed. The following example excerpt from that file shows clustering packages that were not applied because they were not previously installed on the operating system:
cluster.hativoli.server cluster.hativoli.server cluster.hativoli.client cluster.es.server.rte cluster.es.server.rte 5.5.0.0 5.5.0.0 5.5.0.0 5.5.0.0 5.5.0.0 USR USR USR ROOT ROOT APPLY CLEANUP APPLY APPLY CLEANUP FAILED SUCCESS FAILED FAILED FAILED
25
This information is usually located at the end of the log file, or you can search the log file for the name of the file set 2. Take the appropriate action based on what you find in the log file. The level value has not changed If the level value has not changed, then the update was not applied at all. Complete the following steps to solve the problem: 1. See the /var/adm/ras/nim.installp log file for details about the failure. 2. Resolve the failure, or satisfy the dependencies, based on what you find in the log file. 3. Apply the update again.
Installation and migration troubleshooting

This section provides information about problems and workarounds related to installing, uninstalling, and migrating IBM Systems Director.
AIX installation troubleshooting

This section provides information for specific problems and workarounds associated with AIX installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Systems Director Release Notes.
Applications require a different openssl file set version

This problem affects only systems running AIX .
Problem
Certain applications on your system require the rpm version of the openssl file set, but only the default installp version of the openssl file set is available. The following error message is a typical one you will see when this problem occurs:
# ssh exec(): 0509-036 Cannot load program ssh because of the following errors: 0509-150 Dependent module /usr/lib/libcrypto.a(libcrypto.so.0.9.7) could not be loaded. 0509-152 Member libcrypto.so.0.9.7 is not found in archive
Explanation
On AIX , the IBM Systems Director agent and server installation packages install the installp version of the openssl file set. This might cause problems with applications that instead require the older rpm version of the openssl file set. A system can contain both the installp and rpm file sets at the same time. The openssl installp file set installs libraries into /usr/lib and the openssl rpm file set installs libraries into /usr/linux/lib.
Resolution
Use the following command to run applications that depend on the openssl rpm:
#export LIBPATH=/usr/linux/lib:$LIBPATH;
26
Linux installation troubleshooting

This section provides information for specific problems and workarounds associated with Linux installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Systems Director Release Notes.
Error message indicates a supported Linux distribution could not be detected

This problem affects only systems running Linux.
Problem
When installing Platform Agent, Common Agent, or IBM Systems Director Server, the following error message might be generated:
Could not detect rpm supported Linux distribution
where rpm is one of the following RPMs: v For all platforms: IBMCimCore IBMCimExt DirectorCimCore v System x: xSeriesCoreServices-level1 dsa lsi_ir_hhr v Power Systems: pSeriesCoreServices-level1
Explanation
This message occurs if you install IBM Systems Director components on a Linux distribution that is not supported by the following RPMs: v v v v v IBMCimCore IBMCimExt DirectorCimCore xSeriesCoreServices-level1 dsa
v lsi_ir_hhr v pSeriesCoreServices-level1
Resolution
To correct the problem, install a supported Linux distribution. See the IBM Systems Director Planning, Installation, and Configuration Guide for your system.
SELinux is set to enforce security policies

This problem affects only systems running Linux.
27
Problem
You are having trouble installing IBM Systems Director Common Agent because SELinux is in the enforcing state.
Explanation
If your server runs Red Hat Enterprise Linux version 4 or 5, SELinux might be enabled and enforcing security policies on your system. IBM Systems Director Common Agent might have trouble if SELINUX is set to enforcing.
Resolution
You must ensure that SELinux is set to permissive before you install IBM Systems Director Common Agent. See the Preparing to install Common Agent on Linux topic for your system type for more information and instructions.
Cannot install agents on Red Hat Enterprise Linux or VMware managed systems using the Agent Installation Wizard
This problem affects using the Agent Installation Wizard to deploy agents on managed systems running Red Hat Enterprise Linux or VMware ESX. Problem: Attempts to install agents on Red Hat Enterprise Linux or VMware managed systems using the Agent Installation Wizard do not succeed. Investigation: Open the install_root/tpm/config/logs/msg.log file and look for the following lines:
Caused by: at at at at com.jcraft.jsch.JSchException: Algorithm negotiation fail com.jcraft.jsch.Session.receive_kexinit(Session.java:555) com.jcraft.jsch.Session.connect(Session.java:334) com.jcraft.jsch.Session.connect(Session.java:190) com.thinkdynamics.kanaha.de.windows.WindowsSsh.exec(WindowsSsh.java:33)
where install_root is the root directory of your IBM Systems Director installation. If these lines appear in the msg.log file, the problem can be resolved by changing the configuration of the SSH daemon on the VMware system. Resolution: Perform the following steps to ensure that agents can be installed on managed systems running Red Hat Enterprise Linux or VMware ESX using the Agent Installation Wizard: 1. On the VMware managed system, open the /etc/ssh/sshd_config file in a text editor. 2. Locate the following line:
Ciphers aes256-cbc,aes128-cbc
3. Change the line to:

Ciphers aes256-cbc,aes128-cbc,3des-cbc
4. Save and close the /etc/ssh/sshd_config file. 5. Stop and restart the ssh daemon. Type the following command:
service sshd restart
28
6. Use VMware vSphere Client Security Profile Properties to enable ibmsa and ibmcim. a. Using VMware vSphere Client, connect to a VMware ESX 4.x system. b. Click the Configuration tab. c. Under Software, click Security Profile. d. Select Properties and enable ibmsa and ibmcim.
VMware installation troubleshooting

This section provides information for specific problems and workarounds associated with VMware installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Systems Director Release Notes.
This problem affects using the Agent Installation Wizard to deploy agents on managed systems running Red Hat Enterprise Linux or VMware ESX. Problem: Attempts to install agents on Red Hat Enterprise Linux or VMware managed systems using the Agent Installation Wizard do not succeed. Investigation: Open the install_root/tpm/config/logs/msg.log file and look for the following lines:
Caused by: at at at at com.jcraft.jsch.JSchException: Algorithm negotiation fail com.jcraft.jsch.Session.receive_kexinit(Session.java:555) com.jcraft.jsch.Session.connect(Session.java:334) com.jcraft.jsch.Session.connect(Session.java:190) com.thinkdynamics.kanaha.de.windows.WindowsSsh.exec(WindowsSsh.java:33)
where install_root is the root directory of your IBM Systems Director installation. If these lines appear in the msg.log file, the problem can be resolved by changing the configuration of the SSH daemon on the VMware system. Resolution: Perform the following steps to ensure that agents can be installed on managed systems running Red Hat Enterprise Linux or VMware ESX using the Agent Installation Wizard: 1. On the VMware managed system, open the /etc/ssh/sshd_config file in a text editor. 2. Locate the following line:

6. Use VMware vSphere Client Security Profile Properties to enable ibmsa and ibmcim.
29
a. b. c. d.
Using VMware vSphere Client, connect to a VMware ESX 4.x system. Click the Configuration tab. Under Software, click Security Profile. Select Properties and enable ibmsa and ibmcim.
A Platform Agent managed system running VMware 3.5 is discovered as an agentless managed system
This limitation affects Platform Agent managed systems running VMware ESX 3.5 update 3.
Problem
After installing Platform Agent on a managed system running VMware ESX 3.5 update 3, the managed system appears in IBM Systems Director Web interface as an agentless managed system. This problem could occur in one of two circumstances: v The managed system is rebooted after installing Platform Agent but before adding and gaining access to the managed system in IBM Systems Director Web interface. v OpenPegasus is restarted on the managed system after installing Platform Agent but before adding and gaining access to the managed system in IBM Systems Director Web interface.
Explanation
This problem occurs because the version of OpenPegasus that is included with VMware ESX 3.5 update 3 has a built-in SLP service agent. When OpenPegasus starts, it takes control of port 427, removing the registration for the Platform Agent service agent.
Resolution
To resolve this problem after the managed system is rebooted or after OpenPegasus is restarted, issue the following command to start tier1slpinst again:
/etc/init.d/tier1slpinst restart
Note: This command is also used if you cannot request access to the managed system running VMware ESX 3.5 update 2 or update 3.
Windows installation troubleshooting

This section provides information for specific problems and workarounds associated with Windows installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Systems Director Release Notes.
Windows blue screen IRQL_NOT_LESS_OR_EQUAL

This problem affects Common Agent. It occurs only on systems running Windows Server 2003.
30
Problem
During installation of Common Agent, Windows might display the following blue screen trap:
IRQL_NOT_LESS_OR_EQUAL
Resolution
This problem is solved by a Microsoft update. See Microsoft Knowledge Base Article 825236 for more information.
Cannot connect to agents after migration from 6.1.x to 6.2

If you migrate IBM Systems Director Server from 6.1.x to 6.2 and change the location of the product, connectivity problems can result.
Problem
If you use Common Agent, IBM Systems Director Server cannot connect to and manage the local embedded agent if the location of the IBM Systems Director Server installation is moved during migration.
Explanation
If you migrate and change the location of the product, particularly if you move an embedded agent, IBM Systems Director Server cannot connect to the agent.
Resolution
Follow these steps to restore connectivity to the agent. 1. Start IBM Systems Director Server 6.2. 2. Run these commands:
configure.bat -unmanaged -force configure.bat -amhost active_agent_manager_IP_address -passwd active_agent_registration_password -force
Notes: v If your server runs on Windows, active_agent_registration_password is the second password used while installing IBM Systems Director Server (agent manager) using the advanced wizard path. If you used the basic installation path, it is the operating system's administrator password. v If your server does not run on Windows, it is the second password entered during the configAgtMgr.sh step during the IBM Systems Director Server installation. 3. If your server does not run on Windows, replace configure.bat with configure.sh. These files are located here: agent_installation_location/runtime/agent/ toolkit/bin.
Agents are not migrated during migration from 6.1.x to 6.2

If you change agent managers on IBM Systems Director 6.1.x and then upgrade it to IBM Systems Director 6.2, the agents that the previous agent manager managed might not migrate.
31
Problem
When migrating IBM Systems Director6.1.x to 6.2, agents that were managed by a previous agent manager on IBM Systems Director6.1.x are not migrated.
Explanation
If you add another agent manager to IBM Systems Director6.1.x and activate it, the agents that were managed by the previous agent manager are not automatically set up migrated. This causes problems when you perform tasks such as upgrading to IBM Systems Director 6.2. To migrate the agents with IBM Systems Director, you need to ensure that they are associated with the active agent manager.
Resolution
Complete the following steps to migrate all agents that were managed by the previously active agent manager to the new active agent manager before you migrate IBM Systems Director: 1. Run the following commands:
configure.bat -unmanaged -force configure.bat -amhost new_active_agent_manager_IP_address -passwd new_active_agent_registration_password -force
Notes: v If your server runs on Windows, new_active_agent_registration_password is the second password used while installing IBM Systems Director Server (agent manager) using the advanced wizard path. If you used the basic installation path, it is the operating system's administrator password. v If your server does not run on Windows, it is the second password entered during the configAgtMgr.sh step during the IBM Systems Director Server installation. 2. If your server does not run on Windows, replace configure.bat with configure.sh. These files are located here: agent_installation_location/runtime/agent/ toolkit/bin. If you do not complete these steps and migrate to IBM Systems Director 6.2 without the agents, you need to manually migrate the agents to the new active agent manager.
Cannot install agent on managed system

This problem affects installation of agent packages on managed systems using the Agent Installation Wizard from a management server running AIX or Linux.
Problem
When you attempt to install an agent package on a managed system, the package is not installed.
Investigation
Use the following procedure to determine the cause of the problem: 1. In the IBM Systems Director navigation area, expand Task Management and click Active and Scheduled Jobs. 2. On the Active and Scheduled Jobs page, select the job that you want to view and click Actions > Properties.
32
3. On the Properties page, click the Logs tab. v If the status of the agent installation task is Complete with errors, go to step 4. v If the status of the agent installation task is not Complete with errors, then the problem you encountered is not described in this topic. Review the other installation troubleshooting topics or see Getting help and support. 4. Right-click the job activation record for the agent installation task and click Show logs. The log is displayed below the table. 5. Look for either of the following messages in the log for the agent installation that could not be completed:
scp: /tmp/commonagent_tmp/dir6.1_commonagent_linz.sh: No such file or directory
or
File Transfer failed to locate file on the target device
v If either of the preceding messages occurs in the logs, see the Explanation and the Resolution. v If the messages do not occur in the logs, then the problem you encountered is not described in this topic. Review the other installation troubleshooting topics or see Getting help and support.
Explanation
The Expect package (version 5.42 or later) must be installed on the management server in order to distribute agent packages to managed systems using the Agent Installation Wizard. This package is either missing or corrupted.
Resolution
1. Stop IBM Systems Director Server. Type smstop and press Enter. 2. Install (or reinstall) the Expect RPM. 3. Start IBM Systems Director Server. Type smstart and press Enter. 4. Install the agent package. Tip: You can run the agent installation job that did not succeed instead of creating a new job using the Agent Installation Wizard. Click Task Management > Active and Scheduled Jobs, select the agent installation job that did not complete successfully, and then click Run Now.
Installing a version of IBM Systems Director that is earlier than the current version
This problem affects IBM Systems Director on all platforms.
Problem
You already have IBM Systems Director installed on a system and have problems installing another, earlier version of IBM Systems Director. The existing version of IBM Systems Director becomes disabled and the newly-installed earlier version does not work (twgstart fails).
Explanation
You cannot directly install a version of IBM Systems Director on a system that already contains a later version of IBM Systems Director than the one you want to install. You must first completely uninstall the existing IBM Systems Director
33
version, including all data, before installing the earlier IBM Systems Director version.
Resolution
To correct this problem, complete the following steps: 1. Uninstall all versions of IBM Systems Director. 2. Complete any manual cleanup, as described in IBM Systems Director uninstallation fails, that is required for the uninstalled IBM Systems Director versions. 3. Install the earlier IBM Systems Director version.
IBM Systems Director installation hangs and then fails

This problem affects all systems.
Problem
The IBM Systems Director installation process hangs for 30 minutes or more and then fails with the following error:
LWI is taking too long to start. Installer Exiting...
Investigation
The increased installation duration might result from an incorrectly configured nameserver (DNS) on the system or, if a nameserver is not required for your installation, improperly targeted localhost and host name IP addresses.. The following conditions indicate that the nameserver is configured correctly: v The nameserver address or addresses are correct for your network environment. v You are able to connect to valid hosts on the network and validate that the connection occurs within a reasonable amount of time. If resolution of the host names takes a long time, an incorrectly configured nameserver is likely the cause.
Explanation
When starting the server during IBM Systems Director installation, a number of sockets are created. The sockets need to lookup network addresses. If the nameserver is improperly configured, the lookup time duration will be very long and the lookup will then usually fail. This will cause IBM Systems Director Server to take a very long time to start up or even not start up at all.
Resolution
If a nameserver is required for your IBM Systems Director installation, complete the following steps to resolve this problem: 1. Ensure that the nameserver on the system is correctly configured for the network environment. 2. Verify that other hosts on the network can be reached. 3. Try installing IBM Systems Director again.
34
If a nameserver is not required for your IBM Systems Director installation, complete the following steps to resolve this problem: 1. Add the IP address for the localhost and host name to the host file, which you can find in the following location on the management server: v AIX or Linux: /etc/hosts v Windows: %SystemRoot%\system32\drivers\etc\hosts Example:
129.0.2.1 localhost 10.122.126.11 director_server
2. Try installing IBM Systems Director again.
See the Sun Developer Network Bug Database at http://bugs.sun.com/ bugdatabase/view_bug.do?bug_id=5092063 for further information.
IBM Systems Director installation or uninstallation fails and requires cleanup

This problem affects systems on which installation or the removal of an installation failed for a component of IBM Systems Director.
Problem
You attempted to install IBM Systems Director or uninstall a component of IBM Systems Director, but it failed and left behind files, data, or registry settings that might cause problems for later installations.
Explanation
A failed IBM Systems Director installation or uninstallation can leave items that require cleanup.
Resolution
Use the following information to clean up after a failed IBM Systems Director installation or uninstallation: For AIX : If the installation or uninstallation of one or more of the IBM Systems Director file sets fails, take the following actions to clean up your system: v Run installp -C to clean up any interrupted installation processes. v Use the following commands to determine if there are any file sets related to IBM Systems Director that are still on the system:
* * * * lslpp lslpp lslpp lslpp -l -l -l -l | | | | grep grep grep grep -i -i -i -i fspproxy director cas sysmgt.cim
If any of the following file sets are returned by the lslpp command, use the installp -u <filesetname> command to uninstall them in the order in which they are listed here: Director.Server.ext.FSPProxy.rte DirectorServer
35
DirectorCommonAgent cas.agent* Director.DirectorCimCore DirectorPlatformAgent Director.CimExtension Director.CimCore sysmgt.cim.smisproviders.hba_hdr* sysmgt.cim.smisproviders.hhr* sysmgt.cim.smisproviders.vblksrv* sysmgt.cim.providers.smash* sysmgt.cim.providers.osbase* sysmgt.cimserver.pegasus.rte*
Other applications might use these file sets, so remove them with caution. v After uninstallation, complete the following steps to check for unnecessary remaining processes and end them if they are found: 1. Check for CIMprocesses by running the following commands:
# ps -ef | grep cimserver root 491660 499862 0 Oct 15 - 0:00 /opt/freeware/cimom/pegasus/bin/cimservera # ps -ef | grep cimlistener root 454814 1 0 Oct 15 - 0:00 /usr/bin/cimlistener # ps -ef | grep -i diag root 487444 1 0 Oct 15 - 0:00 /opt/freeware/cimom/pegasus/bin/CIM_diagd
2. Check for SLP and SNMP processes by running the following commands:
# ps -ef | grep tier1slp root 442594 1 0 Oct 15 /bin/tier1slp # ps -ef | grep dirsnmp root 303210 1 0 Oct 15 /opt/ibm/icc/cimom/bin/dirsnmpd 0:00 /opt/ibm/director/cimom 0:00
3. Check for server Java processes by running the following commands:

# ps -ef | grep java | grep -i /opt/ibm/director/jre root 372942 1 0 00:45:28 pts/3 4:12 /opt/ibm/director/jre/bin/java -Xms512m -Xmx1024m -Dtio.home=/opt/ibm/director/tpm -Dtc.home=/opt/ibm/director/tpm -Djava.net.preferIPv4Stack=true -Xms512m -Xmx1024m -Dtio.home=/opt/ibm/director/tpm -Dtc.home=/opt/ibm/director/tpm -DPCL_BASEDIR=/opt/ibm/director/data/base -Xbootclasspath/a:/opt/ibm/director/lwi/runtime/core/rcp/eclipse /plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/opt/ibm /director/lwi/lib/ISCJaasModule.jar:/opt/ibm/director/lwi/lib /UsmiJaasModule.jar:/opt/ibm/director/lwi/lib/icl.jar:/opt/ibm /director/lwi/lib/jaas2zos.jar:/opt/ibm/director/lwi/lib /jaasmodule.jar:/opt/ibm/director/lwi/lib/lwinative.jar:/opt/ibm /director/lwi/lib/lwirolemap.jar:/opt/ibm/director/lwi/lib /passutils.jar -Xverify:none -cp eclipse/launch.jar:eclipse /startup.jar:/opt/ibm/director/lwi/runtime/core/rcp/eclipse/plugins /com.ibm.rcp.base_6.1.2.200801281200/launcher.jar com.ibm.lwi.LaunchLWI
4. If a common agent file set was uninstalled, check for agent Java processes by running the following commands:
# ps -ef | grep nonstop root 532710 1 0 10:02:02 - 0:00 bin/nonstop_aix @config /nonstop.properties # ps -ef | grep /var/opt/tivoli/ep root 491666 532710 0 10:02:03 - 1:12 /var/opt/tivoli/ep/_jvm /jre/bin/java -Xmx384m -Xminf0.01 -Xmaxf0.4 -Xbootclasspath/a:/var /opt/tivoli/ep/runtime/core/rcp/eclipse/plugins /com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/var/opt/tivoli /ep/lib/icl.jar:/var/opt/tivoli/ep/lib/jaas2zos.jar:/var/opt/tivoli /ep/lib/jaasmodule.jar:/var/opt/tivoli/ep/lib/lwinative.jar:/var
36
/opt/tivoli/ep/lib/lwirolemap.jar:/var/opt/tivoli/ep/lib /passutils.jar:../../runtime/agent/lib/cas-bootcp.jar -Xverify:none -cp eclipse/launch.jar:eclipse/startup.jar:/var/opt/tivoli/ep/runtime /core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200 /launcher.jar com.ibm.lwi.LaunchLWI
v After uninstallation, the following directories should not exist. Remove them if they still exist: /opt/ibm/director /opt/ibm/icc /etc/ibm/tivoli v After uninstallation, remove the following files only if you are running a version of AIX that is earlier than 6.1: /opt/ibm/director/classes/pConsoleLaunch.jar /opt/ibm/director/classes/extensions/pConsole.TWGExt For more information about cleaning up a failed installation, see Cleaning up a failed software installation in the IBM System p and AIX Information Center. For IBM i: If IBM Systems Director uninstallation fails on IBM i because an object is locked, see the job log for details about the object that caused the failure. Commands such as WRKOBJLCK and DLCOBJ can be used to work with object locks. If a different server has a lock on an IBM Systems Director object, the uninstallation might be completed successfully but the locked IBM Systems Director object might still exist after the uninstallation. If you want to clean up the locked objects, you first might need to end that server to release the locks. Use the normal documented method of ending that server, for example, use ENDTCPSVR instead of ENDJOB. For Linux and VMware: The IBM Systems Director uninstallation script checks for any RPM dependencies. If dependencies are detected, the script lists the dependencies found and then exits. To remove the dependencies, type the following command for each dependency listed:
rpm -ef rpm_name
where rpm_name is the dependency. Note: Occasionally this command might fail. If it does, type rpm -ef rpm_name --noscripts where rpm_name is the dependency. After removing all of the dependencies, run the IBM Systems Director uninstallation script again. For Windows: Contact the IBM Technical Support Center for assistance. You must have an IBM Support Line contract.
Network outage while installing IBM Systems Director Server

This problem affects the re-installation after the first failed installation of IBM Systems Director Server.
Problem
When a network outage occurs during the installation process, it might cause the file set to stay at either the BROKEN or APPLYING state.
37
Explanation
You might experience this problem if, while you are running the IBM Systems Director Server installer from a remote command line, there is a network outage that disconnects you from the remote system.
Resolution
You must uninstall the incomplete IBM Systems Director Server before attempting to reinstall the it. For instructions on how to uninstall and clean up the incomplete installation, see IBM Systems Director installation or uninstallation fails and requires cleanup on page 35.
Installation fails when contacting an agent manager

This problem affects server installation on all platforms.
Problem
CAS installation fails when it tries to contact the agent manager that was specified during IBM Systems Director installation.
Explanation
You are able to enter in any ip address or host name value for the agent manager. There is no validation of the value. If the ip address or host name is actually invalid, CAS cannot make contact with an agent manager and installation fails.
Resolution
Check the CAS installation log for specifics about why it failed. If the error is an invalid agent manager ip address or host name, correct that value to a valid agent manager ip address or host name and reinstall IBM Systems Director.
Uninstallation of Common Agent on SUSE Linux Enterprise Server 9 for System x takes approximately one hour
This problem affects System x systems running SUSE Linux Enterprise Server 9.
Problem
After using IBM Systems Director Server to discover Common Agent on a SUSE Linux Enterprise Server 9 for System x system, uninstalling Common Agent will take approximately one hour. The exact time duration of the uninstallation might vary depending on the hardware configuration of the system on which Common Agent was running.
Investigation
No root cause has been identified.
Explanation
If Common Agent has not been discovered at all after the installation, the uninstallation will take only a few minutes. Once it is discovered, however, the
38
uninstallation takes much longer. This problem does not occur on other operating systems such as SUSE Linux Enterprise Server 10, Red Hat Enterprise Linux, or Windows.
Resolution
Plan for the uninstallation to take a while and then wait while it completes.
Silent installation does not verify settings before installing

This problem affects the silent installation of IBM Systems Director on all supported systems.
Problem
When you perform a silent installation of IBM Systems Director with customized settings, the installation is interrupted after already installing some components.
Explanation
When IBM Systems Director is installed silently, it does not check the settings before it starts the installation. If any of your customized settings are incorrect, the installation is interrupted at the point of the setting's implementation and potentially after some components are installed.
Resolution
Check the customized settings and correct any that are wrong. Then rerun the silent installation.
Configuration data is not preserved after uninstalling IBM Systems Director on Linux on System x
This problem affects Linux on System x systems.
Problem
When you uninstall IBM Systems Director Server or Common Agent on a Linux on System x system, no configuration data is preserved.
Explanation
When the uninstall command is launched, the task to save the configuration data is not launched.
Resolution
If you require the configuration data for another use, ensure that you back it up manually before you uninstall IBM Systems Director.
CIT service error displayed in Event Viewer when installing CAS agent on Windows Server 2008
This problems occurs during the installation of the CAS agent on the 64 bit version of Windows Server 2008.
39
Problem
After completing the CAS agent installation on the 64 bit version of Windows Server 2008 there are two referencing the CITMDRV service on the "Administrative Events" view on in the Event Viewer.
Resolution
The errors can be safely ignored. They do not cause the installation to fail, or affect any function.
A return code with no message text is displayed when deploying Windows agent packages
This issue affects the deployment of Windows agent packages.
Problem
When deploying Windows agent packages, the Agent installation may display a return code with no additional message text to explain the issue.
Resolution
Check thedirinst.log file on the endpoint system to find details about the error.
Service processor troubleshooting

For IBM Systems Director to receive hardware events (alerts) and system health information, you must install the appropriate software for the service processor in your server. This section provides strategies for determining why a service processor is not responding as well as information about determining the correct software to install.
Service processor is unresponsive

This problem affects the Remote Supervisor Adapter and the IPMI baseboard management controller (BMC).
Problem
A service processor is unresponsive in an IBM Systems Director environment.
Resolution
To resolve this problem, review the following considerations: For BMC and Remote Supervisor Adapter models: Make sure the port settings for the service processor are correct. For more information, see Preparing firewalls and proxies for IBM Systems Director in the IBM Systems Director Planning, Installation, and Configuration Guide for your system.Make sure the port settings for the service processor are correct. For Remote Supervisor Adapter models: v Make sure that the affected system has a Remote Supervisor Adapter installed. Inspect the server to make sure a Remote Supervisor Adapter is in its slot.
40
v Make sure that the Remote Supervisor Adapter is in the correct slot. Many servers require that the Remote Supervisor Adapter be installed in a specific slot. See the documentation for the server model to determine the required slot. v Make sure that the Remote Supervisor Adapter has power. The Remote Supervisor Adapter requires its own power and it is separate from the server power supply. v Make sure that the correct firmware is installed. The Remote Supervisor Adapter firmware is specific to operating systems and server models. If the installed firmware is for the correct operating system and server model, make sure that the firmware is at the latest level. v Make sure that the device driver is installed and that it is the correct device driver is active. v Make sure that the Remote Supervisor Adapter is correctly cabled for your network configuration. v Make sure that the Remote Supervisor Adapter is correctly configured for your network.
For DHCP For static IP addresses Make sure the adapter is configured to use DHCP. Make sure the adapter is configured to use an IP address within the correct subnet.
v For the Remote Supervisor Adapter II, if the USB cable is required, make sure that it is attached correctly to a USB port. See the Remote Supervisor Adapter documentation for information about this USB cable. v Make sure that the Remote Supervisor Adapter is configured for the correct operating system. If the system is running Linux, set the Remote Supervisor Adapter operating system setting to Linux; otherwise, set it to Other. For BMC: v Determine whether the affected server has a Remote Supervisor Adapter installed as well. If a server has both a Remote Supervisor Adapter and a BMC, IBM Systems Director ignores the BMC. v (For systems running Linux or Windows) Make sure that the device driver is installed, that it is the correct device driver, and that it is active. Make sure that the device driver is installed, that it is the correct device driver, and that it is active. For detailed information, see Preparing to manage service processors with IBM Systems Director in the IBM Systems Director Planning, Installation, and Configuration Guide for your system. v Make sure that you have the appropriate software installed. The required files are server specific. Make sure that you have the appropriate software installed. The required files are server specific. For detailed information, see Preparing to manage service processors with IBM Systems Directorin the IBM Systems Director Planning, Installation, and Configuration Guide for your system. v (For in-band communication) View the install_root\cimom\logs\ibmipmi.log file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). If this file is not present or the log entries are out of date, then no communication
41
between IBM Systems Director and the BMC has occurred. This file logs any errors associated with loading or communicating with the IBM Mapping Layer or IPMI device driver. v (For out-of-band communication) Turn on ASM library logging to log communication with the service processor. To do so, complete the following steps: 1. Edit the install_root\lwi\runtime\asmlog.cfg file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 2. Change the ASM library log setting:
asmloglevel=verbose
3. Stop IBM Systems Director Server. For Linux or AIX , type smstop on the management server. For Windows, type net stop DirServer. 4. Start IBM Systems Director Server. For Linux or AIX , type smstart on the management server. For Windows, type net start DirServer.
Enabling hardware events

In order for IBM Systems Director to receive hardware events (or alerts) from IBM System x and xSeries servers, the server must have either an IPMI baseboard management controller (BMC) or a Remote Supervisor Adapter II. When a system has both a BMC and a Remote Supervisor Adapter II installed, IBM Systems Director ignores the BMC. Receiving hardware events from your server is called in-band communication. If you want to enable Common Agent or Platform Agent for in-band communication, you must install the appropriate software. Before you do so, you must answer the following questions for each server in your system-management environment: v What is the server model? v Does the server include a BMC? v Does the server include a Remote Supervisor Adapter II? v What operating system is installed on the server? Your answers to these questions determine the software that you must download and install on your systems. If the server has a BMC only: You must download and install the following applicable software. Attention: The following software is specific to server models and operating systems. Your server might not require some of this software. Make sure that you download the correct software and device drivers for your server model and operating system. v The latest BIOS firmware update for the server model v The latest firmware for the BMC v The OSA IPMI device driver v The IBM Mapping Layer software for OSA IPMI v All of the latest device drivers for your operating system, including, but not limited to, network, video, and USB device drivers. These device drivers can affect the service processor. Also, out of date video device drivers can cause Java exceptions. v Any critical updates that might be available for that server
42
Note: The IPMI subsystem in a server consists of the BMC (the hardware controller for the IPMI subsystem), sensors, buses, other controllers, and a protocol for communication. The OSA IPMI device driver communicates with all controllers in the IPMI subsystem. If the server has a BMC and a Remote Supervisor Adapter II: When a Remote Supervisor Adapter II is installed, IBM Systems Director ignores the BMC. See the instructions for a server that has a Remote Supervisor Adapter II. If the server has a Remote Supervisor Adapter II or Remote Supervisor Adapter: You must download and install the following software. Attention: The following software is specific to server models and operating systems. Your server might not require some of this software. Make sure that you download the correct software and device drivers for your server model and operating system. v The latest BIOS firmware update for the server model v The latest Remote Supervisor Adapter II firmware v All of the latest device drivers for your operating system, including, but not limited to, network, video, and USB device drivers. These device drivers can affect the service processor. v Any critical updates that might be available for that server v If the server has a BMC, the OSA IPMI device driver. This driver is required if you want to update the BMC firmware using the Software Distribution task. To make sure you download and install all of the latest drivers and software for your server, print out the Downloads and drivers list from the IBM Support Web site. Use this page as a check list to make sure you have the latest BIOS, firmware, and device drivers. Complete the following steps: 1. Go to the IBM Support Web site at www.ibm.com/servers/eserver/support/ xseries/index.html. 2. In the Product family list, select your server model. 3. In the Type list, select the type if applicable. 4. In the Model list, select the model if applicable. 5. In the Operating system list, select your operating system installed on that server. 6. Click Go. 7. Print the Software and device drivers Web page to use as a check list. You might have to print more than one page.
Unknown error message is displayed when using SLES

There is a problem with SLES that causes an IBM Systems Director to be configured incorrectly.
Problem
When you start Systems Director, an Unknown error message is displayed on multiple task views.
Resolution
To resolve this problem, follow these steps:
43
1. In the /etc/hosts file on the affected managed system, comment out the 127.0.0.2 entry. Insert the pound sign symbol (#) in the first character position of the entry, for example:
# 127.0.0.2 server.company.com server
2. Use the smstop command to stop the management server. For more information, see smstop command in the IBM Systems Director Commands Reference. 3. Use the smstart command to restart the management server. For more information, see smstart command in the IBM Systems Director Commands Reference. 4. Open the IBM Systems Director Web interface and start the affected task again.
Database configuration troubleshooting

This section provides information about problems and workarounds for databases used with IBM Systems Director. These problems include database configuration.
Errors occur during the Oracle Database configuration

This problem affects Oracle Database databases only.
Problem
When an Oracle Database database is used, errors occur during the database configuration process.
Investigation
Configure and start the Oracle Database TCP/IP listener before starting the database configuration task. If a failure occurs, check the configuration of the TCP/IP listener.
ORA-00604 error from the Oracle Database

This problem affects management servers that use the Oracle Database only.
Problem
By default, IBM Systems Director caches prepared statements that typically open a cursor with the database. The number of open cursors can grow to exceed the maximum defined for the database, resulting in a ORA-00604 error from the Oracle Database.
Resolution
Increase the Oracle OPEN_CURSORS property or change the IBM Systems Director statement cache size in /lwi/conf/overrides/database.properties file. To change the OPEN_CURSORS property, either update the Oracle Database init.ora file or use the ALTER SYSTEM command to update the SPFILE (System Parameter File). It is recommended that you specify an OPEN_CURSORS value that is 25% larger than the maximum number of statements IBM Systems Director will cache. This can be calculated by taking the sum of the products of the maxActive and maxOpenPreparedStatement properties for each definition in the database.properties file. The following examples illustrates how to calculate the OPEN_CURSORS value.
44
================================= rcs.maxActive = 3 rcs.maxOpenPreparedStatements = 1000 usmi.maxActive = 3 usmi.maxOpenPreparedStatements = 200 ================================= OPEN_CURSORS setting = ((3*100) + (3*200)) * 1.25
Oracle Database 10g Release 2 administrator client will not install on Red Hat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10
This problem affects Red Hat Enterprise Linux, version 5.0, and SUSE Linux Enterprise Server 10 servers on which you are trying to install the Oracle Database 10g Release 2 (10.2) client.
Problem
When attempting to install the Oracle Database 10.2 administrator client on Red Hat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10, the installation fails and indicates that the operating system is not supported with the following error message:
./runInstaller Starting Oracle Universal Installer... Checking installer requirements... Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2 Failed <<<<
Explanation
Oracle Database 10.2 was released before Red Hat Enterprise Linux, version 5.0, and SUSE Linux Enterprise Server 10, so the base installation media does not make provisions for installing the client on those operating systems.
Resolution
You need to work around this issue until Oracle develops a permanent solution for the problem. Choose one of the following two solutions and complete the steps to bypass the operating system check during the client installation: Solution 1 (recommended): Skip the operating system check Run the following command to instruct the Oracle Universal Installer (OUI) to skip the step where it checks the operating system:
% ./runInstaller -ignoreSysPrereqs
Solution 2: Manually configure the OUI to accept the unsupported operating as supported Note: This is a detailed example of the workaround for Red Hat Enterprise Linux, version 5.0, though it might also work for SUSE Linux Enterprise Server 10. Complete the following steps to manually add Red Hat Enterprise Linux, version 5.0, to the list of certified operating system versions: 1. Open oraparam.ini in an editor:
45
v If you are installing Oracle Database 10.2 from the DVD, copy the <path>/database/install/oraparam.ini file (where <path> is the base location of the OUI; the location into which you unzipped the installation files) to a temporary directory, for example to /tmp. v If you are installing Oracle Database 10.2 from an OTN download or have copied the Oracle Database 10.2 media to disk, take a backup of <path>/database/install/oraparam.ini. 2. Edit oraparam.ini to add Red Hat Enterprise Linux, version 5.0, to the [Certified Versions] list. The changed section should match the following text:
[Certified Versions] Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2,redhat-5
3. Start the OUI: v If you copied oraparam.ini to /tmp, run the following command to start the OUI:
% ./runInstaller -paramFile /tmp/oraparam.ini
v If you edited <path>/database/install/oraparam.ini on disk, just start the OUI as normal. 4. Open <path>/database/stage/prereq/db/refhost.xml in an editor. 5. Find the location in the code where the Red Hat Enterprise Linux, version 4.0, checking ends and the SUSE Linux Enterprise Server 9 checking starts, which will serve as the location of a new section of code:
... <PROPERTY NAME="rmem_default" VALUE="262144" /> <PROPERTY NAME="rmem_max" VALUE="262144" /> <PROPERTY NAME="wmem_default" VALUE="262144" /> <PROPERTY NAME="wmem_max" VALUE="262144" /> </KERNEL> </OPERATING_SYSTEM> ++++++ future location of new code section ++++++ <OPERATING_SYSTEM> <VERSION VALUE="9"/> <ARCHITECTURE VALUE="x86"/> <NAME VALUE="Linux"/> <VENDOR VALUE="SuSE"/> ...
6. Add the following code section in the location suggested above:

<OPERATING_SYSTEM> <VERSION VALUE="5"/> <ARCHITECTURE VALUE="x86"/> <NAME VALUE="Linux"/> <VENDOR VALUE="redhat"/> <GLIBC ATLEAST="2.5-12"> </GLIBC> <PACKAGES> <PACKAGE NAME="make" VERSION="3.81" /> <PACKAGE NAME="binutils" VERSION="2.17" /> <PACKAGE NAME="gcc" VERSION="4.1" /> <PACKAGE NAME="libaio" VERSION="0.3.106" /> </PACKAGES> <KERNEL> <PROPERTY NAME="semmsl" NAME2="semmsl2" VALUE="250" /> <PROPERTY NAME="semmns" VALUE="32000" /> <PROPERTY NAME="semopm" VALUE="100" /> <PROPERTY NAME="semmni" VALUE="128" /> <PROPERTY NAME="shmmax" VALUE="536870912" />
46
<PROPERTY NAME="shmmni" VALUE="4096" /> <PROPERTY NAME="shmall" VALUE="2097152" /> <PROPERTY NAME="file-max" VALUE="65536" /> <PROPERTY NAME="VERSION" VALUE="2.6.9" /> <PROPERTY NAME="ip_local_port_range" ATLEAST="1024" ATMOST="65000" /> <PROPERTY NAME="rmem_default" VALUE="262144" /> <PROPERTY NAME="rmem_max" VALUE="262144" /> <PROPERTY NAME="wmem_default" VALUE="262144" /> <PROPERTY NAME="wmem_max" VALUE="262144" /> </KERNEL> </OPERATING_SYSTEM>
Note: For a client installation, use the following entry for the refhost.xml file:
<OPERATING_SYSTEM> <VERSION VALUE="5"/> <ARCHITECTURE VALUE="x86"/> <NAME VALUE="Linux"/> <VENDOR VALUE="redhat"/> <PACKAGES> <PACKAGE NAME="make" VERSION="3.81" /> <PACKAGE NAME="binutils" VERSION="2.17" /> <PACKAGE NAME="gcc" VERSION="4.1" /> </PACKAGES> </OPERATING_SYSTEM>
7. Save the changes to refhost.xml and perform the Oracle Database 10.2 software installation. Note: After you complete this workaround, you still might encounter errors during installation. If so, see Oracle Database 10g Release 2 administrator client installation on Linux on Power Systems throws errors for further information.
Oracle Database 10g Release 2 administrator client installation on Linux on Power Systems throws errors
This problem affects Red Hat Enterprise Linux, version 5.0, SUSE Linux Enterprise Server 10, and SUSE Linux Enterprise Server 11 on Linux on Power Systems after you have already implemented the workaround described in Oracle Database 10g Release 2 administrator client will not install on Red Hat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10.
Problem
After you have already implemented the workaround described in Oracle Database 10g Release 2 administrator client will not install on Red Hat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10 and the Oracle Database 10g Release 2 administrator client installer passes the prerequisite check and begins installing on Linux on Power Systems, you might encounter make or link errors.
Explanation
These errors might occur because additional prerequisite rpms were not installed on the system before beginning the Oracle Database 10g Release 2 administrator client installation.
Resolution
Complete the following steps to resolve this issue.
47
1. Log on as root to verify that all the prerequisites have been met. Unlike when installing the Oracle Database client on Linux on System x, you must install IBM XL C/C++ Advanced Edition V7.0 or you will see link errors during installation. You can download the product and view installation instructions on the IBM Systems Director Downloads Web Site at www.ibm.com/systems/ management/director/downloads/. Ensure that the following packages are installed on your operating system: v IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment Component v xlsmp.msg.rte-1.5.1-3 v xlsmp.rte-1.5.1-3 v vacpp.rte-7.0.1-3 v vac.lib-7.0.1-0 2. Enter the following commands to create the oracle user, set up the oinstall and dba groups, and add the oracle user to the groups: v groupadd oinstall v groupadd dba v useradd g oinstall G dba oracle 3. Ensure that /home/oracle is the home directory for the oracle user and that the user has write permission to this directory. When you create the oracle user, Linux usually creates the home directory automatically, but you should always verify this. Important: IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment Component is not completely compatible with SUSE Linux Enterprise Server 10 or SUSE Linux Enterprise Server 11. Therefore, you need to force the installation of these packages on the operating system. Although there are IBM XL C/C++ packages that compatible with SUSE Linux Enterprise Server 10 and SUSE Linux Enterprise Server 11, you will receive link errors during installation of the Oracle Database 10g2 client if you install them. Use the --nodeps option to install, as in the following example:
rpm rpm rpm rpm -ivh -ivh -ivh -ivh xlsmp.msg.rte-1.5.0-5.ppc64.rpm xlsmp.rte-1.5.0-5.ppc64.rpm --nodeps vacpp.rte-7.0.0-5.ppc64.rpm --nodeps vac.lib-7.0.0-0.ppc64.rpm --nodeps
Unable to connect to the database

IBM Systems Director is unable to connect to the database or loses database connectivity.
Problem
If IBM Systems Director is unable to connect to the database or loses connectivity, unexpected results may occur. This could be caused by v Improper database configuration during installation. v Errors when switching to a new database. v Network problems. v Errors with the database itself.
48
Investigation
Database problems will result in entries in the IBM Systems Director error logs. By default, these logs are stored in install_path\lwi\logs. Database error log entries are normally identified by ?SQLException? preceding the actual error text. If the error message itself does not seem to clearly identify the problem, a web search for the error text can sometimes prove useful. The accompanying stack trace may also be used to further identify the problem. For instance, if the stack trace contained a method name of ?getConnection?, it could be assumed that IBM Director is having problems connecting to the database. If there are method names like ?executeQuery?, ?insert?, ?update?, or ?delete?, those would imply IBM Director had successfully obtained a connection at one point and is now trying to use it. If you are having problems starting the server on an AIX or Linux system that uses IBM DB2 as the database application, look at the install_path\lwi\logs log files. A common error message is one that says: com.ibm.db2.jcc.b.SqlException: Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: db2jcct2 (Not found in java.library.path): ERRORCODE=-4472, SQLSTATE=null. If you see this message, review your environment variables to ensure that the LD_LIBRARY_PATH (for Linux) or LIBPATH (for AIX ) environment variable is set properly. On 64-bit systems, the environment variables must point to the 64-bit database library versions. If the errors occur on IBM Systems Director startup and appear to be ?getConnection? problems, then the database configuration would be the most common problem. Consult the documentation for database configuration for more information. If the configuration steps have been correctly followed, then ensure that the database itself is functional. Additional information may be found in the logs specific to the database you are using. If you are using the supplied Derby database, the log would be in install_path\lwi\logs as derby.log. For the other databases (DB2, Oracle, and SQLServer) the database administrator may need to be contacted. If the errors occur after IBM Director has been running successfully, then the problem would most likely be a network problem if the database is remote, or a problem with the database itself. These would also require examination of the various log files and possible database administrator involvement.
Explanation
The symptoms of database connection problems vary. If the database was improperly configured during installation or after switching to a new database, IBM Systems Director may not fully start. The same may hold true if the database itself is not functioning. If the database is on a remote machine, then network problems at IBM Systems Director startup may also cause IBM Systems Director to not fully start.
Database data is not displayed after database restart

This problem affects IBM Systems Director on all platforms
49
Problem
While IBM Systems Director Server is active, connectivity to the underlying database is lost. Loss of connectivity can result from any number of situations, including but not limited to network problems, database server problems, and authentication problems. After database connectivity is recovered (by restarting the database application server, recovering the network issue, or so on), however, all IBM Systems Director Web interface pages that should display information retrieved from the database display no database information.
Explanation
Loss of communication with the database invalidates the pooled connections. Multiple applications within IBM Systems Director use these connections. Transactions on these connections are now in an unknown state, which puts IBM Systems Director in an unknown state.
Resolution
Stop IBM Systems Director Server, ensure that the database is available and accessible, then restart IBM Systems Director Server.
Poor Performance when the IBM Systems Director server is configured with Microsoft SQL Server 2005 configuration
The web console or command line interface for IBM Systems Director Server may become slow to respond when configured with a Microsoft SQL 2005 Server.
Problem
The web console or command line interface for IBM Systems Director Server may become slow to respond when configured with a Microsoft SQL Server 2005. After a period of inactivity, the smcli and Web console may hang or become slow to respond during operations requiring access to a remote Microsoft SQL Server 2005 Server. Note: The Web console responses may appear normal until an SQL access is required. When the hang condition is detected, the <Install_Root>/IBM/Director/ lwi/logs/error-log-<x>.html file will contain the following entries:
SEVERE SQLException <operation being attempted, i.e., SELECT> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
Resolution
Add the following parameters to the <Install_Root>/IBM/Director/lwi/conf/ overrides/database.properties file:
rcs.testOnBorrow = true rcs.validationQuery = select 1 rcs.testWhileIdle=true rcs.timeBetweenEvictionRunsMillis=60000 rcs.minEvictableIdleTimeMillis=300000 usmi.testOnBorrow = true usmi.validationQuery = select 1 usmi.testWhileIdle=true usmi.timeBetweenEvictionRunsMillis=60000 usmi.minEvictableIdleTimeMillis=300000
The IBM Systems Director Server must be restarted for the changes to take effect.
50
smrestore fails when IBM DB2 is configured to require approval of restore operation
This problem affects IBM Systems Director with IBM DB2.
Problem
If your IBM DB2 database was configured to require approval of restore operations, the smrestore command will fail during upgrade to IBM Systems Director 6.2.
Explanation
The smrestore command begins the process of restoring data. For IBM DB2, this process includes a rollforward operation. If approval is required, the rollforward operation cannot complete without user intervention, and therefore the process of restoring data cannot complete. This causes smrestore to fail.
Resolution
If your database was configured to require approval of restore operations, you should disable that option. v To determine if your database is set to require approval of restore operations, run the following command on your IBM DB2 server, where db_name is the name of your IBM Systems Director database.
db2 get db cfg for db_name
The output of this command includes lines for the following parameters: LOGRETAIN, LOGARCHMETH1, and LOGARCHMETH2. If any of these parameters are set to RECOVER or a state other than OFF, this indicates that the data cannot be restored without user intervention. smrestore fails to handle this situation. v To resolve the issue when smrestore fails to restore the database because approval is required, complete the following steps. 1. Locate the install_root\proddata\dbconfig\sql\db2\db2Restore.cmd file, where install_root is the root directory of your IBM Systems Director installation. For AIX and Linux, look for the db2Restore.sh script. This file includes information like the following example:
db2 RESTORE DATABASE %TC_DB% USER %USERNAME% USING %PASSWORD% FROM %BACKUP_DIR% TAKEN AT %TIMESTAMP% WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING
2. Edit the script with a text editor and change the value to include the WITHOUT ROLLING FORWARD option as in the following example:
db2 RESTORE DATABASE %TC_DB% USER %USERNAME% USING %PASSWORD% FROM %BACKUP_DIR% TAKEN AT %TIMESTAMP% WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT ROLLING FORWARD WITHOUT PROMPTING
3. Run the smrestore command again. v To avoid problems in the future with smrestore failing to restore the database because approval is required, set the LOGRETAIN, LOGARCHMETH1, or LOGARCHMETH2 parameter to OFF. To set a parameter to OFF, run the following command on your IBM DB2 server, where db_name is the name of your IBM Systems Director database, and log_parameter is the parameter that must be set to OFF:
db2 update db cfg for db_name using log_parameter no
51
Unable to access Log in page for IBM Systems Director

This problem affects the Firefox Web browser.
Problem
When you try to connect to IBM Systems Director using the Firefox Web browser, the browser might not let you display the secure Web page.
Investigation
IBM Systems Director uses a self-signed certificate unless the system administrator has replaced the certificate. The browser configuration determines how the browser handles Web pages that use self-signed certificates. If the browser does not allow you to decide whether the certificate can be trusted, then you might not be able to display the Web page with your current Web-browser settings.
Explanation
A self-signed certificate created and used initially by IBM Systems Director typically will not be marked as trusted by your browser. If your browser permits you to add an exception and therefore mark the certificate as trusted, you can continue.
Resolution
If, when a self-signed certificate is detected, your browser is configured to display a message and not continue, then no link is provided by the browser to add an exception. Note: The browser also might have this behavior after updating to a newer version of the browser. If your browser is configured to display an error message with a link that permits adding an exception, but the browser only displays an error message, changing the specific value for browser.xul.error_pages.enabled and then changing it back might make the browser work correctly. Before changing your browser in about:config, see http://kb.mozillazine.org/Browser.xul.error_pages.enabled.
To permanently avoid this problem, replace the self-signed certificate with one created by a Certificate Authority that Web browsers already trust. You can purchase and use a certificate from a public Certificate Authority. To temporarily avoid this problem, use a different Web browser that permits you to decide whether to trust the certificate.
Logging into IBM Systems Director Server fails

This problem affects the IBM Systems Director Web interface when logging into IBM Systems Director Server.
52
Problem
When you attempt to log into IBM Systems Director Server using the IBM Systems Director Web interface, the following error message is displayed:
Login failed. Check the user ID and password and try again.
This problem can occur when logging into the management server either locally or remotely.
Investigation
Before resolving this problem, review the following considerations: v Make sure the password is correct and that the Caps Lock and Num Lk keys are not on. v Make sure the password does not require updating. v Make sure the password has not expired in the user registry (local operating system, domain, or LDAP). v Make sure the user is not locked or disabled in the user registry (local operating system, domain, or LDAP). v Make sure you are not locked out of IBM Systems Director. If you failed to login 5 or more times, you are locked out of IBM Systems Director.
Resolution
To resolve this problem, complete the applicable steps: If you failed to login 5 or more times: At a command prompt, type the following command to unlock your user name:
smcli chuser -m unlock user_name
where user_name is the locked user name. Note: You must be an SMAdministrator to use this command. If IBM Systems Director Server was installed using a local administrator user name: v Restart the IBM Systems Director Support Program service by typing net start dirserver. v In the IBM Systems Director Web interface Login window, make sure you provide your user ID in one of the following formats: user_name computer_name\user_name domain_name\user_name If IBM Systems Director Server was installed using a domain administrator user name: v Try using a Local System account instead of a Domain account. v In the IBM Systems Director Web interface Login window, make sure you provide the login information using the following formats:
Login window field User ID Password Login information Domain"\"Director Service Account Password
53
v Restart the IBM Systems Director Support Program service by typing net start dirserver.
IBM Systems Director Server troubleshooting

This section provides information about problems and workarounds for IBM Systems Director Server. Some IBM Systems Director Server problems might seem to be problems with the IBM Systems Director Web interface. Review all troubleshooting topics for possible solutions.
An IBM Systems Director Server manageable resource shows offline after discovering its agent
This problem affects IBM Systems Director Server after agent discovery.
Problem
This problem typically occurs when an operating system is discovered and the operating system shows up on the IBM Systems Director Web interface with access Locked. After access is requested, the operating system displays OK for access and a server is discovered. However, the server status then changes to offline.
Investigation
This can happen on Linux or Windows if the server has a Base Management Controller (BMC), the operating system has IPMI Drivers loaded, and the IBM Systems Director Server doesnt have network access to the BMC. Essentially, the IBM Systems Director Server is unable to communicate with the BMC on the server. To investigate, you can perform the following checks: v Check that you can ping the BMC address. If you dont know the BMC address, show the properties for the server and see if you can ping the IP addresses listed on that property page. For more information on viewing properties, see Viewing properties. v If you cannot ping the BMC there is a network access issue. Check to make sure the BMC is connected to the network. v If the BMC is connected to the network, find out if it has a private IP address that is not accessible by the IBM Systems Director Server. v If it doesnt have a private IP address, it could be that it is configured incorrectly. You will have to configure it to a IP address that the IBM Systems Director Server has network access to.
Explanation
IBM Systems Director Server needs network access to both the operating system and the BMC. The BMC provides hardware management, including powering the server on or off and receiving hardware status events. Because of BMC's management functionality, IBM Systems Director Server monitors its connection with the BMC. The BMC needs to be configured with an IP that the IBM Systems Director Server has network access to so that it can be correctly managed.
54
Resolution
To resolve this problem, establish network connectivity from the IBM Systems Director Server to the BMC on the discovered server and then perform the Verify connection task on the server to regain the online indication. Note: The server access state will probably displayLocked, so you will have to request access to the server using the userid and password for the BMC. The servers access state will then move to the OK state.
IBM Systems Director Server fails to start

This problem affects IBM Systems Director Server after you have reinstalled it.
Problem
After you have uninstalled and then reinstalled IBM Systems Director Server, it fails to start.
Resolution
To resolve this problem, complete one or more of these procedures: v Verify that the DNS server and host entries are correct. v On the management server, use the smreset command to reset the database. See the IBM Systems Director Commands Reference for more information.
IBM Systems Director causes network traffic

This problem affects the IBM Systems Director network environment and the management server.
Problem
IBM Systems Director Server causes a large amount of network traffic.
Explanation
To reduce network traffic, you must disable dynamic ping. For Windows You must disable Presence Check.
Resolution
To resolve this problem, complete the applicable steps. For a management server running Windows 1. On the management server, type regedit at a command line, and then press Enter: 2. Navigate to the registry entry HKEY_LOCAL_MACHINE/ SOFTWARE/Tivoli/Director/CurrentVersion. 3. In the right pane, right-click in the pane New > DWORD value. 4. Type DynamicPingInterval for the new DWORD. 5. Right-click DynamicPingInterval and click Modify. 6. In the Value data field, type 0. 7. Click OK.
55
8. Restart the management server.
IBM Systems Director Server not receiving event indications

This problem can occur on all platforms that communicate with IBM Systems Director Server using the Common Information Model (CIM).
Problem
You use IBM Systems Director to perform tasks, but you do not see the expected outcome. For example, you create a virtual server but it does not appear in IBM Systems Director. You delete a virtual server, but it is not removed from IBM Systems Director. You perform power management tasks, but the power states of the systems do not change.
Explanation
The system or platform manager might be unable to contact the IBM Systems Director Server.
Resolution
Check the following items to ensure that the system or platform manager can communicate with IBM Systems Director Server: v Make sure that no firewalls are blocking communication. v Check that the CIM ports for both IBM Systems Director Server and the managed system are open. For more information, see the Ports for IBM Systems Director Server and Ports for managed systems.
Problems exist on IBM i systems with IBM Director Agent version 5.20 installed
This problem affects IBM i systems running IBM Director Agent version 5.20.
Problem
IBM i systems that have IBM Director Agent version 5.20 installed and are managed by IBM Systems Director do not perform as expected. For example, inventory collection fails.
Explanation
The Common Information Model (CIM) server might not be running.
Resolution
The IBM i managed systems running IBM Director Agent version 5.20 must have CIM running to function correctly. To start the CIM server on the IBM i managed systems, run the following IBM i command:
STRTCPSVR *CIMOM
With CIM running on the managed systems, IBM Systems Director Server will gather the missing information on its next scheduled verification of the agent.
56
Trace and error log files are not created

IBM Systems Director trace and error log files are not created in the expected directory.
Problem
If you start IBM Systems Director Server with JConsole enabled, the IBM Systems Director trace and error log files are not created in the install_root\lwi\logs directory, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
Resolution
To resolve this problem, complete the following steps: 1. Stop IBM Systems Director Server by typing the applicable command:
For Linux or AIX For Windows smstop net stop DirServer
2. Add the following properties to the install_root\lwi\conf\overrides\ director.javaopt file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
-Dcom.sun.management.jmxremote.port=11111 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.config.class=com.ibm.rcp.core.internal.logger.boot.LoggerConfig -Dcom.ibm.rcp.core.logger.boot.config.file=../../conf/logging.properties -Drcp.data=../../
3. Start IBM Systems Director Server by typing the applicable command:

For Linux or AIX For Windows smstart net start DirServer
If you want to connect from a remote JConsole, you must change a setting in the install_root\lwi\conf\overrides\USMIKernel.properties file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Change the default IP address in the following line to the IP address of the management server (the server on which IBM Systems Director Server is running):
java.rmi.server.hostname=127.0.0.1
where 127.0.0.1 is the default IP address that you must change.
Uncertain if IBM Systems Director Server is running

This problem affects IBM Systems Director Server.
57
Problem
You are not sure if IBM Systems Director Server is running.
Resolution
To check whether the management server is running, complete the following applicable procedure: v (Windows) On the management server, in the Windows system tray located in the lower-right corner of the desktop, view the IBM Systems Director status icon. A green circle is displayed when IBM Systems Director Server is running. v (AIX and Linux) From a command prompt on the affected management server, type the following command and press Enter:
install_root/bin/smstatus
where install_root is the root directory of your IBM Systems Director installation. The current status of IBM Systems Director Server is displayed.
User is locked out of IBM Systems Director

This problem affects the IBM Systems Director Web interface and Common-Agent managed resources. The problem occurs only on management servers (IBM Systems Director Server) running Linux.
Problem
A user is locked out of IBM Systems Director after unsuccessfully trying five times to log in to the IBM Systems Director Web interface.
Resolution
To correct this problem, type one of the following commands on the management server to reset the locked-out user ID: v smcli chuser -m unlock username where username is the locked-out user ID. v smcli chuser -m reset username where username is the locked-out user ID. v pam_tally --user username --reset where username is the locked-out user ID. If you want to change the number of permitted login failures, edit the /etc/pam.d/ibmdir file on the management server.
Each time a user successfully or unsuccessfully attempts to log in to the IBM Systems Director Web interface, the pluggable authentication module (PAM) increments the login count. After five attempts, the user ID can be locked out. To avoid this problem, you can reset the user login count back to zero after a successful login by editing the /etc/pam.conf file on the management server. Add the following line to the account section of the file and save it:
account required pam_tally.so deny=5 onerr=fail per_user no_lock_time
Note: The deny=5, onerr=fail, per_user, and no_lock_time parameters passed to pam_tally might vary depending on your network configuration. Use the appropriate parameters and values for your network environment.
58
Common Agent and Platform Agent troubleshooting

This section provides information about problems and workarounds for Common Agent and Platform Agent. Some Common Agent and Platform Agent problems might be problems with other IBM Systems Director components. Review all troubleshooting topics for possible solutions.
Extraneous CIM indication errors appear in the system log on Linux

This problem affects Platform Agent managed systems and Common Agent managed systems running Linux.
Problem
Extraneous error messages appear in the system log stating that the CIM server did not deliver an indication, as in the following example:
cimserver[18682]: PGS10405: Failed to deliver an indication: PGS10800: CIMXMLINDICATIONHANDLER ERROR: CIM_ERR_FAILED: A GENERAL ERROR OCCURRED THAT IS NOT COVERED BY A MORE SPECIFIC ERROR CODE.: "Cannot load module (SMSConsumer:SMSConsumer): Unknown exception."
Explanation
This is a limitation in IBM Systems Director 6.1. The LSIIndicationSettings.dat file that is used to define some default CIM indications is the same for both Windows and Linux installations; however, the SMS consumer is not available on managed systems running Linux.
Resolution
The extraneous errors can be ignored. Alternatively, you can use the cimsubscribe command to delete the subscriptions that are causing the extraneous error messages. From a command prompt on the managed system, issue the following commands:
cimsubscribe -n cimsubscribe -n Failed" -hn cimsubscribe -n cimsubscribe -n cimsubscribe -n cimsubscribe -n -hn "SMS" cimsubscribe -n cimsubscribe -n cimsubscribe -n cimsubscribe -n cimsubscribe -n cimsubscribe -n cimsubscribe -n root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 "SMS" root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive Failed" -hn "SMS" -ds -fn "RAID Physical Drive Part of Logical Drive -ds -ds -ds -ds -ds -ds -ds -ds -ds -ds -ds -fn -fn -fn -fn -fn -fn -fn -fn -fn -fn -fn "RAID "RAID "RAID "RAID "RAID "RAID "RAID "RAID "RAID "RAID "RAID Physical Drive Added" -hn "SMS" Hot Spare Created" -hn "SMS" Hot Spare Failed" -hn "SMS" Physical Drive becomes Hot Spare" Logical Drive Offline" -hn "SMS" Logical Drive Degraded" -hn "SMS" Logical Drive Optimal" -hn "SMS" Physical Drive PFA" -hn "SMS" Rebuild Started" -hn "SMS" Rebuild Complete" -hn "SMS" Rebuild Failed" -hn "SMS"
Managed resource does not send events

This problem affects managed resources running VMware ESX 3.0.
59
Problem
Managed resources running VMware ESX 3.0 do not send in-band events to IBM Systems Director Server.
Explanation
The OpenIPMI drivers are not enabled by the VMware ESX 3.0 operating system, causing these managed resources not to send in-band events to IBM Systems Director.
Resolution
This problem is fixed by ESX Server 3.0.0 patch ESX-8005537. Obtain download and installation instructions for this patch from the following Web site: kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC &externalId=8005537.
You cannot promote Platform Agent to Common Agent on Linux with Xen
This limitation affects installing Common Agent on Platform Agent managed systems running with the Xen kernel.
Problem
If you have previously installed Platform Agent on a Platform Agent managed system running with the Xen kernel, installing Common Agent on the managed system does not succeed. An error message like the following one is displayed:
Promotion of an IBM Systems Director Platform Agent with Xen support to a IBM Systems Director Common Agent is not supported.
Explanation
When Platform Agent is installed, it installs two providers (cmpi-xen and ibmvm-imagesupport) that cause conflicts when you later install Common Agent.
Resolution
Uninstall Platform Agent, and then install Common Agent.
This problem affects using the Agent Installation Wizard to deploy agents on managed systems running Red Hat Enterprise Linux or VMware ESX.
Problem
Attempts to install agents on Red Hat Enterprise Linux or VMware managed systems using the Agent Installation Wizard do not succeed.
Investigation
Open the install_root/tpm/config/logs/msg.log file and look for the following lines:
60
Caused by: at at at at
com.jcraft.jsch.JSchException: Algorithm negotiation fail com.jcraft.jsch.Session.receive_kexinit(Session.java:555) com.jcraft.jsch.Session.connect(Session.java:334) com.jcraft.jsch.Session.connect(Session.java:190) com.thinkdynamics.kanaha.de.windows.WindowsSsh.exec(WindowsSsh.java:33)
where install_root is the root directory of your IBM Systems Director installation. If these lines appear in the msg.log file, the problem can be resolved by changing the configuration of the SSH daemon on the VMware system.
Resolution
Perform the following steps to ensure that agents can be installed on managed systems running Red Hat Enterprise Linux or VMware ESX using the Agent Installation Wizard: 1. On the VMware managed system, open the /etc/ssh/sshd_config file in a text editor. 2. Locate the following line:

6. Use VMware vSphere Client Security Profile Properties to enable ibmsa and ibmcim. a. b. c. d. Using VMware vSphere Client, connect to a VMware ESX 4.x system. Click the Configuration tab. Under Software, click Security Profile. Select Properties and enable ibmsa and ibmcim.
Cannot install agent on managed system

This problem affects installation of agent packages on managed systems using the Agent Installation Wizard from a management server running AIX or Linux.
Problem
When you attempt to install an agent package on a managed system, the package is not installed.
Investigation
Use the following procedure to determine the cause of the problem: 1. In the IBM Systems Director navigation area, expand Task Management and click Active and Scheduled Jobs. 2. On the Active and Scheduled Jobs page, select the job that you want to view and click Actions > Properties. 3. On the Properties page, click the Logs tab. v If the status of the agent installation task is Complete with errors, go to step 4 on page 33. v If the status of the agent installation task is not Complete with errors, then the problem you encountered is not described in this topic. Review the other installation troubleshooting topics or see Getting help and support. 4. Right-click the job activation record for the agent installation task and click Show logs. The log is displayed below the table.
61
5. Look for either of the following messages in the log for the agent installation that could not be completed:
scp: /tmp/commonagent_tmp/dir6.1_commonagent_linz.sh: No such file or directory
or
File Transfer failed to locate file on the target device
v If either of the preceding messages occurs in the logs, see the Explanation on page 33 and the Resolution on page 33. v If the messages do not occur in the logs, then the problem you encountered is not described in this topic. Review the other installation troubleshooting topics or see Getting help and support.
Explanation
The Expect package (version 5.42 or later) must be installed on the management server in order to distribute agent packages to managed systems using the Agent Installation Wizard. This package is either missing or corrupted.
Resolution
1. Stop IBM Systems Director Server. Type smstop and press Enter. 2. Install (or reinstall) the Expect RPM. 3. Start IBM Systems Director Server. Type smstart and press Enter. 4. Install the agent package. Tip: You can run the agent installation job that did not succeed instead of creating a new job using the Agent Installation Wizard. Click Task Management > Active and Scheduled Jobs, select the agent installation job that did not complete successfully, and then click Run Now.
Common Agent cannot be installed on an AIX or Linux system

When installing Common Agent on an AIX or LINUX system using the Agent Installation Wizard, the installation completes with errors, but Common Agent is not installed on the target system.
Explanation
When installing Common Agent on an AIX or Linux system, IBM Systems Director uses SSH to copy the installer to the target system and perform the installation. It stores the SSH public key into the /root/.ssh/known_hosts file on the IBM Systems Director Server. If the public key stored on the IBM Systems Director Server is not valid, the installation of the Common Agent will not complete successfully.
Investigation
After the installation of Common Agent completes with errors, look for an error similar to the following in the Event Log:
ERROR [Deployment Request 10081] (LDOWorker.java:231) engine.LDOWorker: COPDEX040E An unexpected deployment engine exception occurred: class com.thinkdynamics.kanaha.de.DeploymentException:COPCOM123E A shell command error occurred: Exit code=255, Error stream="@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
62
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending key in /root/.ssh/known_hosts:9 RSA host key for X.XXX.XXX.XXX has changed and you have requested strict checking. Host key verification failed.
Resolution
Perform these steps: 1. Gather public keys for all managed systems that reported that the Common Agent completed with errors described in the Investigation section. 2. Compare the results to either the user's known_hosts file, the /etc/ssh/ssh_known_hosts file, or both. 3. Update the user's known_hosts file or the /etc/ssh/ssh_known_hosts file to match the public keys for the managed systems. 4. Attempt to install Common Agent again. Related reference SSH Host Key Protection
Installing Common Agent on managed systems with IBM Director Agent version 5.20 does not succeed
This problem affects using the Agent Installation Wizard task to install Common Agent on managed systems with IBM Director Agent version 5.20.
Problem
When you select multiple systems on which to install Common Agent using the Agent Installation Wizard, if some systems are running IBM Director Agent version 5.20 and some systems are not running IBM Director Agent version 5.20, installation of Common Agent does not succeed on the systems that are running IBM Director Agent version 5.20.
Explanation
Resolution
When you install Common Agent on systems that are running IBM Director Agent version 5.20, ensure that all the selected systems are running IBM Director Agent version 5.20, and wait for the installations to complete before beginning installations on other systems.
63
A discovered agent displays an unexpected managed system

This problem affects Common Agent 6.1.0.3 on AIX .
Problem
An agent is discovered with an unexpected managed system after requesting access.
Explanation
There are two methods that you can use to install Common Agent 6.1.0.3 on AIX : v Install Common Agent 6.1.0.3 with the base operating system using an AIX 5.3 TL10 or AIX 6.1 TL03 operating system installation. v Install Common Agent 6.1.0.3 manually from the image on the Web. There is a problem with the manual installation of Common Agent 6.1.0.3 that is downloaded from the Web. The agent is discovered with an unexpected managed system after requesting access. This problem does not exist if you install Common Agent 6.1.0.3 with the AIX 5.3 TL10 or AIX 6.1 TL03 base operating system. Note: This issue is not related to IBM Systems Director Server.
Resolution
If you have not yet discovered the agent, restart the agent manually by running the following two commands:
INSTALL_ROOT/agent/runtime/agent/bin/endpoint.sh stop INSTALL_ROOT/agent/runtime/agent/bin/endpoint.sh start
If you installed Common Agent 6.1.0.3 manually from the image on the Web and see the extra managed system, complete the following steps to resolve the problem: 1. Delete the managed systems from IBM Systems Director Server. 2. Restart the agent. 3. Discover the agent. 4. Request access to the agent. 5. Verify that only two managed systems are shown.
Unable to upgrade L2 agent to Common Agent on VMware ESX Server 3.5 or Red Hat Enterprise Linux 5.3 hosts
This problem affects upgrades of managed resources running VMware ESX Server 3.5 or Red Hat Enterprise Linux 5.3.
Problem
When using the /Release Management/Agents Install/ function to upgrade an endpoint running VMware ESX Server 3.5 or Red Hat Enterprise Linux 5.3 to Common Agent, Common Agent is not installed correctly. The uninstall script is not available on the agent system.
64
Resolution
To upgrade the VMware ESX Server 3.5 host or Red Hat Enterprise Linux 5.3 host to Common Agent, manually copy the Common Agent installer to the system and run the installer on that system.
IBM Systems Director, version 6.1.1, Platform Agent installed on systems with an Integrated Management Processor (iMM) requires an Intelligent Platform Management Interface (IPMI) driver
This problem affects IBM Systems Director, version 6.1.1, Platform Agents installed on systems with an Integrated Management Processor (iMM).
Problem
IBM Systems Director, version 6.1.1, Platform Agent installed on systems with an Integrated Management Processor (iMM), requires an Intelligent Platform Management Interface (IPMI) driver, which is distributed with the operating System to generate in-band alerts.
Explanation
Base Windows 2003 operating systems installed on systems with iMM will not be able to generate in-band alerts. However, iMM on systems with Windows 2003 will send out-of-band alerts to IBM Systems Director Server to prevent users from losing functionality.
Resolution
To enable IPMI driver on Windows 2008 and Windows 2003 R2, see Managing IPMI Devices in Windows 2003 R2 and Windows 2008 in the IBM Systems Director Best Practices RedWiki. Linux and VMware operating systems can use openIPMI driver, which is distributed with the operating system itself. Related reference Managing IPMI Devices in Windows 2003 R2 and Windows 2008
Platform Agent 5.20.3x installation fails on systems with Citrix XenApp

This problem affects IBM Systems Director 6.1 systems that use the Citrix XenApp drive remap function.
Problem
Platform Agent 5.20.3x fails to install properly.
Explanation
You used the remap function of Citrix XenApp to change the drive letter of the intended installation drive, but the regular installation of Platform Agent 5.20.3x cannot tell this and so fails.
65
Resolution
Install Platform Agent 5.20.3x with edited response files to point the installation to the correct drive letter. Complete the following steps to do this for each component. 1. Obtain the necessary Platform Agent 5.20.3x installation and response files. 2. Edit the response file to change the target drive (TARGETDRIVE=x setting) to whichever drive is specified by the Citrix XenApp drive remap function. Save the response file. 3. Install Platform Agent 5.20.3x using the response file.
Common Agent does not start when the host name is set to localhost or the name server is not setup correctly
The Common Agent process is running, but /opt/ibm/director/agent/bin/ lwistatus.sh returns "INACTIVE".
Explanation
The Common Agent doesn't work when the host name is set to localhost or the name server is not setup correctly.
Resolution
Configure the host name and name server correctly and then restart the Common Agent.
Installation of the common agent on AIX fails to start LWI

Installation of the common agent on AIX fails with the message: LWI is taking too long to start.
Problem
Installation of the common agent on AIX fails with the message:
LWI is taking too long to start.
Explanation
If IPv6 is enabled on an AIX system, (IPv6 is enabled by default), and no IPv6 loopback address is defined in its /etc/hosts, resolving ::1 might time out when there is a DNS configured and the DNS server is not responding to requests of type AAAA..
Resolution
1. IPv6 is enabled: if the ifconfig command returns something similar to this:
# ifconfig -a | grep inet6 inet6 ::1/0
2. Add the following line to the system's /etc/hosts file:

::1 loopback localhost # IPv6 loopback (lo0) name/address
3. Add the following line to the system's /etc/netsvc.conf to ensure that the address lookup consults /etc/hosts first before trying DNS resolution:
hosts = local , bind
66
IBM Director Agent version 5.20.x agents automatically change to offline state in IBM Systems Director 6.x
This problem affects IBM Systems Director 6.x.
Problem
In IBM Systems Director 6.x, the status of IBM Director Agent version 5.20.x agents might automatically change between online and offline.
Explanation
This issue is intermittent and caused by either or both increased load or poor performance, for example due to insufficient memory, on IBM Systems Director Server.
Resolution
In the IBM Systems Director Web interface, navigate to Settings > Server Preferences and gradually increase the values of the Verify Connection and Query Vital Properties interval settings for all resource types until the issue disappears. Tip: A setting of one hour for the Verify Connection interval and six hours for the Query Vital Properties interval should suffice for most environments.
Web interface troubleshooting

These problems can occur when you try to open the Web interface or when you are working with your resources in the interface.
Add Criterion window stops updating

This problem affects the Microsoft Internet Explorer browser.
Problem
When working in the Create Group wizard, if you use the keyboard instead of the mouse to click OK after entering criteria in the Add Criterion window, the window stops updating.
Resolution
To resolve this problem, complete one of the following steps: v Close the Add Criterion window and open it again. v Use the mouse instead of the keyboard to click OK.
Certificate has not been signed by a trusted authority

This problem affects Microsoft Internet Explorer and Mozilla Firefox Web browsers.
Problem
When you try to open the IBM Systems Director Web interface, the following message or window is displayed: For Microsoft Internet Explorer
67
A security message indicates that there is a problem with the security certificate; the security certificate was not issued by a trusted certificate authority. The message might tell you to determine whether you want to trust the certifying authority, or it might strongly recommend that you close the Web page. The message might be slightly different depending on the installed version of Internet Explorer or Java Runtime Environment (JRE) and the JRE provider. For Mozilla Firefox The Website Certified by an Unknown Authority window is displayed.
Explanation
These types of messages indicate that your browser has examined the Secure Sockets Layer (SSL) certificate it received from the server and has determined that the certificate was not issued by a trusted certificate authority.
Resolution
To resolve the problem, complete the applicable steps: For Microsoft Internet Explorer Complete the following actions depending on the message that is displayed:
Table 1. Message descriptions and suggested actions Message description Suggested actions
The message indicates that you can view the Choose one of the following actions: certificate to determine whether you want to Temporary solution: trust the certifying authority. Click View Certificate and Install Certificate to install the certificate and instruct the browser to trust the server. Permanent solution: Replace the default certificate with a certificate signed by a certificate authority (CA). For more information, see Configuring Secure Sockets Layer between IBM Systems Director and the Web browser client.
68
Table 1. Message descriptions and suggested actions (continued) Message description The message provides a recommendation that you close the Web page and do not continue to the Web site. Suggested actions Choose one of the following actions: Temporary solution: Complete the following steps: 1. Click Continue to this website to open the Web interface. Note: The message might indicate that continuing to the Web site is not recommended. However, you can proceed to the Web site to login to IBM Systems Director Web interface and install the certificate temporarily. 2. Login to IBM Systems Director Web interface. 3. Click Certificate Error. A message is displayed indicating that the certificate presented by this Web site was not issued by a trusted certificate authority. 4. Click View certificates. A message is displayed indicating that the CA Root certificate is not trusted. 5. Click Install Certificate to install the certificate and instruct the browser to trust the server. Permanent solution: Complete the following steps: 1. Click Click here to close this webpage. 2. Replace the default certificate with a certificate signed by a certificate authority (CA). For more information, see Configuring Secure Sockets Layer between IBM Systems Director and the Web browser client.
For Mozilla Firefox To resolve this problem, complete the applicable step: Temporary solution: Select Accept this certificate permanently to install the certificate and instruct the browser to trust the server, and click OK. Permanent solution: Replace the default certificate with a certificate signed by a
69
certificate authority (CA). For more information, see Configuring Secure Sockets Layer between IBM Systems Director and the Web browser client.
Firebug Firefox extension might cause unpredictable behavior in the IBM Systems Director Web interface
This problem affects Mozilla Firefox Web browsers that have the Firebug extension installed.
Problem
The Firebug extension for Firefox might cause Web-browser applications to behave erratically. If Firebug is enabled in Firefox, the IBM Systems Director Web interface might react slowly or have unpredictable behavior.
Resolution
To resolve this problem, disable the Firebug extension when using the IBM Systems Director Web interface. For information about disabling Firebug, see the Firebug documentation.
Internet Explorer fails to display the IBM Systems Director Web interface
This problem affects Microsoft Internet Explorer 7 Web browsers that are running on Windows Vista.
Problem
The Internet Explorer 7 Web browser fails to display and cannot login to the IBM Systems Director Web interface on a system running Windows Vista, Mozilla Firefox running on the same Vista system can log into the IBM Systems Director Web interface.
Resolution
Make sure that the Internet Explorer 7 Web browser uses Java 5 Service Refresh 5 (SR5) or later.
Login message displays corrupt characters

After running the dircli chgloginmsg command, the customized login message contains corrupted characters for some languages.
Problem
When creating a customized login message as described in Changing the welcome message on the login screen (publib.boulder.ibm.com/infocenter/systems/topic/UNKNOWN_PLUGIN/ fqm0_c_changing_login_herald.html), you must store the text of the message in a property files. Property files are not compiled into byte codes. Therefore, there is no way to tell the Java Virtual Machine (JVM) which character set to use. When a property file is loaded from a stream, the ISO 8859-1 character encoding is used. The characters are corrupted if they cannot be directly represented in this encoding.
70
Resolution
The contents of the loginMessage_xx.properties file needs to be created in ASCII or encoded in with Unicode-escape sequences. Initially, create the customized login message file (loginMessage_xx.properties) so that it is encoded in UTF-8, then convert the file to escaped Unicode using a Java utility program such as native2ascii. 1. Create and save an initial version of the loginMessage_xx.properties file in UTF-8. For example, using Microsoft Windows Notepad, use the Save As... option to specify UTF-8 in the Encoding field. 2. Run the native2ascii utility (located in the JDK/bin directory) against the UTF-8 encoded property file. For example: native2ascii encoding UTF-8 sourcefile.txt targetFile.txt 3. Run the dircli chgloginmsg command against the property file.
Navigation pane is not displayed correctly during initial log in

This problem occurs only when you log in immediately after installing IBM Systems Director Server.
Problem
After installing IBM Systems Director Server, if you log in immediately, the IBM Systems Director navigation pane might not be displayed correctly. You might see a list of navigation elements instead of the expandable navigation items.
Resolution
Log out and wait ten minutes. Then, log in again.
No results found when using Find a Resource

This problem affects the Find a Resource task when searching for a resource with a name containing a single quote.
Problem
When trying to locate a resource that has a single quote (') in its name, if you add the single quote character around the search string, Find a Resource will fail to find the resource.
Resolution
To resolve this problem, search for the resource using other characters in the name instead of the single quote.
Panels display translated text in multiple languages

This problem occurs only when viewing pages in the IBM Systems Director Web interface in languages other than English.
Problem
After changing the language setting in your browser, sometimes translated strings (words or phrases) in the IBM Systems Director Web interface display in multiple languages. When the problem occurs, some strings may display in the newly selected language and other strings may display in the original language.
71
Resolution
When you change languages for your browser, complete the following steps to ensure that the IBM Systems Director Web interface does not display translated strings in both the previously selected and the newly selected languages. Note: For more information, refer to the help documentation for your browser. 1. Change the language for your browser. 2. Clear the browser cache. 3. Close the browser. Make sure to close all open browser windows or tabs. 4. Restart the browser.
Panels display truncated text in non-English languages

This problem occurs only when viewing pages in the IBM Systems Director Web interface in languages other than English.
Problem
When your browser is set to a non-English language, some page elements in the IBM Systems Director Web interface display truncated strings (words or phrases). The truncation is caused when the translated string is longer than the English string. This kind of problem occurs most frequently in elements like table cells or buttons. Sometimes, the panel border truncates an element that has been enlarged because of the longer translated string.
Resolution
Change your system to use a larger screen resolution. Changing the resolution may not fix all occurrences of truncated text.
Pop-up window does not close

This only occurs when you use a Firefox 2.0 browser and IBM Systems Director Server running on SUSE Linux Enterprise Server 10.
Problem
The window headers on pop-up windows remain open after you click OK or Cancel. This can occur for the following pop-up windows: v Context chooser v Add to dashboard v Delete and other confirmation windows.
Resolution
There are two possible resolutions: 1. Right click on the window header of the pop-up window. From the context menu, select This Frame > Reload Frame to refresh the frame and close the window header. 2. Download and install the latest version of Mozilla Firefox.
72
Security certificate is not valid

This problem affects the Microsoft Internet Explorer and Mozilla Firefox Web browser.
Problem
Microsoft Internet Explorer When you try to open the IBM Systems Director Web interface, the Security Alert window is displayed. The message indicates that the security certificate is not valid or does not match the name of the site. Note: The message might be slightly different depending on the installed version of the Java Runtime Environment (JRE) and the provider. For Mozilla Firefox version 2.0 When you try to open the IBM Systems Director Web interface, the Security Error: Domain Name Mismatch window is displayed with the following information:
You have attempted to establish a connection with address. However, the security certificate presented belongs to address.apex.company.com.
where address is the address of the Web browser. For Mozilla Firefox version 3.0 When you try to open the IBM Systems Director Web interface, the Secure Connection Failed page is displayed with the following information:
address:port uses an invalid security certificate. The certificate is not trusted because it is self signed. The certificate is only valid for address
where v address is the address of the Web browser. v port is the port number used by the Web browser. One of the following error codes are displayed: v sec_error_untrusted_issuer v sec_error_caPcert_invalid
Explanation
The message indicates that the host name you specified in the URL to access the IBM Systems Director Web interface is different than the host name specified in the Common Name (CN) field of the Secure Sockets Layer (SSL) certificate that is stored on the management server.
Resolution
To resolve this problem, complete the applicable step: v Change the host name in the URL to match the CN. v Change the CN in the SSL certificate to match the host name in the URL. The CN designated in the IBM Systems Director Web interface default certificate is set to the long name of the host system. For information about how to change the CN in the SSL certificate, see Configuring Secure Sockets Layer between IBM Systems Director and the Web browser client in the IBM Systems Director Systems Management Guide.
73
Then, click OK to prevent the message from displaying again for future connections to the server during this browser session.
Unpredictable results occur when two users log into IBM Systems Director Server using the same browser application
IBM Systems Director does not support different users logging in from the same Web browser application.
Problem
If you log into IBM Systems Director using a web browser and then log into IBM Systems Director again using the same browser application from the same system, unpredictable results, including empty web pages, may occur in both browser sessions.
Explanation
This problem occurs when using browsers from the same browser application because each Web browser instance uses the same session. Most web applications, including IBM Systems Director, assume there is a unique session for each user but that is not the case in this situation. IBM Systems Director does not support different users logging in using the same browser application from the same system, whether the sessions are in different tabs or different windows. Note: Although a single user cannot log in multiple times, you can establish multiple sessions for a user account in the same browser on the same system using multisession support.
Unable to connect to Web interface with SUSE Linux Enterprise Server 10

This problem affects the Mozilla Firefox browser when running on SUSE Linux Enterprise Server 10.
Problem
When you attempt to display the IBM Systems Director Web interface using the Mozilla Firefox Web browser on a system running SUSE Linux Enterprise Server 10, the following message is displayed:
YourSystem received a message with incorrect Message Authentication Code. If the error occurs frequently contact the website administrator.
where YourSystem is the system on which you are using the Web browser.
Explanation
A problem with SUSE Linux Enterprise Server 10 has been reported to Novell.
Resolution
To resolve this problem, download and install the latest version of Mozilla Firefox.
Unable to export information

This problem affects the Microsoft Internet Explorer and Mozilla Firefox Web browsers.
74
Problem
You are unable to export information from a table view or topology view in the IBM Systems Director Web interface.
Resolution
Complete the following applicable steps: For Microsoft Internet Explorer Make sure that the browser is set to enable automatic prompting for file downloads. To verify, complete the following task: 1. Click Internet Options > Security and click Custom level. 2. In the Security Settings - Internet Zone window, ensure that Downloads > Automatic prompting for file downloads > Enable is selected. 3. Try the export task again. Make sure that the option to block pop-up windows is disabled for the Web address that is used by IBM Systems Director Server. To verify, complete the following steps: 1. Click Tools > Internet Options. 2. In the Internet Options window, click the Privacy tab. 3. In the Pop-up Blocker area, if Block pop-ups is selected, click Settings. 4. In the Pop-up Blocker Settings window, in the Address of Web site to allow field, type the Web address of IBM Systems Director Server. 5. Click Add. 6. Click Close. 7. In the Options window, click Apply and then OK. For Mozilla Firefox Make sure that the option to block pop-up windows is disabled for the Web address that is used by IBM Systems Director Server. To verify, complete the following steps: 1. Click Tools > Options. 2. In the Options window, click the Content tab. 3. Next to the Block pop-up windows check box, click Exceptions. 4. In the Allowed Sites - Popups window, in the Address of web site field, type the Web address of IBM Systems Director Server. 5. Click Allow. 6. Click Close. 7. Click OK in the Options window.
Unable to print information

Problem
You are unable to print information from a table view or topology view in the IBM Systems Director Web interface.
75
Resolution
Complete the following applicable steps: For Microsoft Internet Explorer Make sure that the option to block pop-up windows is disabled for the Web address that is used by IBM Systems Director Server. To verify, complete the following steps: 1. Click Tools > Internet Options. 2. In the Internet Options window, click the Privacy tab. 3. In the Pop-up Blocker area, if Block pop-ups is selected, click Settings. 4. In the Pop-up Blocker Settings window, in the Address of Web site to allow field, type the Web address of IBM Systems Director Server. 5. Click Add. 6. Click Close. 7. In the Options window, click Apply and then OK. For Mozilla Firefox Make sure that the option to block pop-up windows is disabled for the Web address that is used by IBM Systems Director Server. To verify, complete the following steps: 1. Click Tools > Options. 2. In the Options window, click the Content tab. 3. Next to the Block pop-up windows check box, click Exceptions. 4. In the Allowed Sites - Popups window, in the Address of web site field, type the Web address of IBM Systems Director Server. 5. Click Allow. 6. Click Close. 7. Click OK in the Options window.
The IBM Systems Director Web interface does not perform as expected when browsing
This problem affects Microsoft Internet Explorer Web browsers that have Enhanced Security Configuration enabled and are running on Windows Server 2003 or Windows Server 2008.
Problem
By default, Internet Explorer Enhanced Security Configuration is enabled on Windows Server 2003 and Windows Server 2008. When you start Internet Explorer, the following message is displayed:
Microsoft Internet Explorers Enhanced Security Configuration is currently enabled on your server. This enhanced level of security reduces the risk of attack from Web-based content that is not secure, but it may also prevent Web sites from displaying correctly and restrict access to network resources.
When using a Web browser with Enhanced Security Configuration enabled, some properties of the IBM Systems Director Web interface might not display as expected.
76
Explanation
Internet Explorer Enhanced Security Configuration establishes a configuration for your server and for Internet Explorer that decreases the exposure of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites might not display or perform as expected.
Resolution
Using a server for Internet browsing is not a good security practice because Internet browsing increases the exposure of your server to potential security attacks. It is a best practice recommendation that you run your Web browser on a system that is not a server. However, if you must use a server running Windows Server, you must turn off Internet Explorer Enhanced Security Configuration. Complete the following applicable steps to disable Internet Explorer Enhanced Security: Windows Server 2003 Complete the following steps: 1. Click Start > Control Panel. 2. In the Control Panel window, click Add or Remove Programs. 3. Click Add/Remove Windows Components. 4. Clear the Select Internet Explorer Enhanced Security Configuration check box. 5. Click Next; then, click Finish. Windows Server 2008 Complete the following steps: 1. Close any instances of the Internet Explorer Web browser. 2. Start Server Manager. 3. In the Details pane, locate the Security Information area that is displayed under the Server Summary area. 4. In the Security Information area, click Configure IE ESC. 5. In the Internet Explorer Enhanced Security Configuration window, click the applicable option: v If your user account is a member of the Administrators group, click Off under Administrators. v If your user account is a member of a standard users group, click Off under Users. 6. Click OK.
Welcome page is not displayed during initial log in

This problem occurs only when you log in to the IBM Systems Director Web interface immediately after installing IBM Systems Director Server.
Problem
After installing and starting IBM Systems Director Server, if you log in to the IBM Systems Director Web interface immediately, the full IBM Systems Director Welcome page might not be displayed. You might instead see either the default Welcome page or only a Page cannot be displayed or Page not found error message.
77
Explanation
The server is started but not yet fully active. This situation can occur on any platform but is more prominent on Windows because the server is automatically started at the end of installation. The green circle status indicator in the system tray will appear, but it can be misleading because the server might not have fully started yet.
Resolution
Log out and wait ten minutes. Then, log in again. Some server startup time durations are long, so keep trying if you continue to not see the full Welcome page.
Columns are empty in Navigate Resources

This problem affects IBM Systems Director Web interface 6.x on Windows.
Problem
When you navigate resources in IBM Systems Director 6.x, cells in the optional Primary Owner Name and Primary Owner Contact columns are always blank.
Explanation
The feature related to these two properties was removed from IBM Systems Director 6.x, but the two columns were left in the table.
Resolution
Do not plan to assign these two properties when completing tasks such as creating a dynamic group.
Launched tasks troubleshooting

These problems affect your browser when you try to start a launched task or when you try to launch a program, such as the IBM Systems Director Launched Tasks program, from the IBM Systems Director Web interface.
Contents of the launch[x].jnlp file are displayed

This problem affects the Microsoft Internet Explorer and Firefox Web browsers.
Problem
When you try to start a launched task, the contents of the launch[x].jnlp file are displayed.
Explanation
The .jnlp extension is mapped incorrectly.
Resolution
To map the .jnlp extension to the Java Web Start executable file, complete the following applicable step:
78
For Microsoft Internet Explorer Complete the steps in Updating the Microsoft Internet Explorer Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide. For Mozilla Firefox Complete the steps in Updating the Firefox Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide.
A download window is displayed

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.
Problem
When you try to start a launched task, one of the following windows is displayed: v (Firefox) Downloads v (Firefox) Download Manager v (Internet Explorer) File Download In Internet Explorer, a message might be displayed that asks if you want to save a file or indicates a file cannot be downloaded from the server.
Resolution
To resolve this problem, complete the following steps: For Firefox Complete the following steps: 1. In the browser, click Tools > Options. 2. In the Options window, click the Main tab. 3. Clear the Show Download Manager when a download begins check box. 4. Click OK. For Internet Explorer Complete one or more of the following actions: v Make sure that you have installed all software updates for the version of Internet Explorer that you are using. Use Windows Update to access software updates for Internet Explorer. v Java Web Start (JWS) software is required to enable the launched-tasks feature in IBM Systems Director. If the error message includes a link to a Web site, click the link to download JWS. Alternatively, complete the steps in Downloading Java Web Start in the IBM Systems Director Systems Management Guide. v Click Tools > Internet Options > Advanced. Make sure that Do not save encrypted pages to disk is not selected. v The .jnlp extension might not be mapped to the Java Web Start executable file. To map the .jnlp extension to the Java Web Start executable file, complete the procedure detailed in Updating the Microsoft Internet Explorer Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide. v The .jnlp extension is mapped to the Java Web Start executable file, but the Launch action is not defined.
79
To define the Launch action, complete the following steps: 1. In Windows Explorer, click Tools > Folder Options. 2. Click the File Types tab, select JNLP in the Registered file types list, and click Advanced. 3. In the Edit File Type window, clear the Confirm open after download check box and click New. 4. In the New Action window, specify the following information and click OK: In the Action field, type &Launch. In the Application used to perform action field, click Browse, select and specify the javaws.exe under a JRE that is installed on your browser system using the following format:
"XXXXXXXX" "%1"
Select Use DDE. The window expands. - In the Application field, type javaws. - In the Topic field, type System. 5. In the Edit File Type window, click OK. 6. In the Folder Options window, click OK. 7. Close Windows Explorer. 8. Retry to the affected launched task.
Empty window is displayed or nothing happens

Problem
When you try to start a launched task, an empty window is displayed or nothing happens in your Web browser.
Resolution
Complete one or more of the following actions: For all browsers v Java Web Start (JWS) software is required to enable the launched-tasks feature in IBM Systems Director. If the error message includes a link to a Web site, click the link to download JWS. Alternatively, complete the steps in Downloading Java Web Start in the IBM Systems Director Systems Management Guide. v Make sure that the system on which IBM Systems Director Server is installed is not blocked by a pop-up blocker on your browser system. For example, check for a pop-up blocker displayed under the Address bar, and make sure it is turned off. For Internet Explorer v Click Tools > Internet Options > Advanced. Make sure that Do not save encrypted pages to disk is not selected. v (Internet Explorer 7 only) Complete the following steps: 1. Click Tools > Internet Options > Security. 2. Click Custom level.
80
3. In the Security Settings - Internet Zone window, make sure that Downloads > Automatic prompting for file downloads > Enable is selected. v The .jnlp extension might not be mapped to the Java Web Start executable file. To map the .jnlp extension to the Java Web Start executable file, complete the procedure detailed in Updating the Microsoft Internet Explorer Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide. v The .jnlp extension is mapped to the Java Web Start executable file, but the Launch action is not defined. To define the Launch action, complete the following steps: 1. In Windows Explorer, click Tools > Folder Options. 2. Click the File Types tab, select JNLP in the Registered file types list, and click Advanced. 3. In the Edit File Type window, clear the Confirm open after download check box and click New. 4. In the New Action window, specify the following information and click OK: In the Action field, type &Launch. In the Application used to perform action field, click Browse, select and specify the javaws.exe under a JRE that is installed on your browser system using the following format:
"XXXXXXXX" "%1"
Select Use DDE. The window expands. - In the Application field, type javaws. 5. 6. 7. 8. - In the Topic field, type System. In the Edit File Type window, click OK. In the Folder Options window, click OK. Close Windows Explorer. Retry to the affected launched task.
For Mozilla Firefox Complete the procedure detailed in Updating the Firefox Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide. Try the task again. The Opening launch.jnlp message might be displayed. The message asks you what you want to do with the .jnlp file. To make sure that the launched task can proceed and that this message will not be displayed in the future, it is recommended that you select Open with Java Web Start Executable and Do this automatically for files like this from now on.
A host name mismatch is detected

This problem affects Microsoft Internet Explorer and Mozilla Firefox Web browsers.
Problem
When you try to start a launched task, the following message is displayed:
Warning - HTTPS: Hostname Mismatch
81
The message indicates that the host name in the server security certificate does not match the name of the server and asks you if you want to proceed.
Explanation
This message means that the host name you specified in the URL to access the Web interface is different than the host name specified in the Common Name (CN) field of the Secure Sockets Layer (SSL) certificate that is stored on the server system. Notes: 1. The message might be slightly different depending on the installed version of Java Runtime Environment (JRE) and the provider. 2. (Windows only) The Warning - HTTPS: Hostname Mismatch message window might be hidden behind the browser window. In this case, the Web interface seems to hang. Press Alt + Tab on the keyboard to bring the message window to the foreground.
Resolution
You must change either the CN in the SSL certificate to match the host name in the URL, or you must change the host name in the URL to match the CN. The CN designated in the IBM Systems Director default certificate is set to the long name of the host system. For more information about how to change the CN in the SSL certificate, see Configuring Secure Sockets Layer (SSL) between IBM Systems Director and the Web browser client in the IBM Systems Director Systems Management Guide.
Java Web Start - Download Error window is displayed

This problem affects the Mozilla Firefox and Microsoft Internet Explorer browsers.
Problem
When you try to start a launched task, the Java Web Start - Download Error window is displayed. The message indicates that Java Web Start is unable to launch the task.
Explanation
For Mozilla Firefox browsers, this message is displayed when you receive the Opening launch.jnlp message and choose to run the javaws executable from a non-system Java Runtime Environment (JRE), such as the IBM Systems Director JRE. This message can also be displayed when Microsoft Internet Explorer is configured to use a Web proxy server that is running Microsoft Internet Security and Acceleration (ISA) Server or Microsoft Forefront Threat Management Gateway, Medium Business Edition, and when no exception has been made for the IBM Launched Tasks program. The IBM Launched Tasks program uses Secure Sockets Layer (SSL), so an exception needs to be granted.
Resolution
For Mozilla Firefox:
82
Complete the procedure detailed in Updating the Firefox Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide. Try the task again. The Opening launch.jnlp message might be displayed. The message asks you what you want to do with the .jnlp file. To make sure that the launched task can proceed and that this message will not be displayed in the future, it is recommended that you select Open with Java Web Start Executable and Do this automatically for files like this from now on. For Internet Explorer: Update your ISA server or gateway to allow an exception for your server. Try the task again.
Java Web Start fails because correct IP address cannot be determined

Problem
When you try to start a launch-in-context task from IBM Systems Director, the Java Web Start - Download Error window is displayed. When you click Details button in the window, the error indicates that Java Web Start is unable to load a resource.
Explanation
In environments where the server has multiple network interface cards or multiple IP addresses associated with the server, the launch-in-context task might be unable to determine the correct IP address of IBM Systems Director server to use to download files for the launch. When this problem occurs, the launch fails.
Resolution
On the IBM Systems Director Server, complete the following steps: 1. Go to the following directory: (Director install location)lwi\runtime\ USMiConsole\eclipse\plugins\com.ibm.usmi.console.lic_x.x.x\WEB-INF\ classes, where x.x.x indicates the most current com.ibm.usmi.console.lic directory. 2. Use a text editor to edit the lic.properties file. 3. At the end of the file, add the following line: serverIPAddress=xx.xx.xx.xx, where xx.xx.xx.xx is the IP address for the IBM Systems Director Server from which the launch-in-context task must retrieve files for the task launch. 4. Save your changes and close the lic.properties file. 5. Restart IBM Systems Director and then start the launch-in-context task again.
Java Web Start fails due to JARS signed with multiple certificates
When attempting to launch any of the Launched Tasks UIs, Java Web Start fails due to JARS signed with multiple certificates.
83
Problem
After updating to IBM Systems Director version 6.1.2, you might receive an error when running any Launched Tasks using Java Web Start. The error window will contain the heading Java Web Start - Launch File Error and the message will state Unable to launch IBM Launched Tasks.
Investigation
To investigate this problem, complete the following steps: 1. Click Details in the message window. Several labeled tabs will display. 2. Click the General tab. You will see the following message:
An error occured while launching/running the application. Title: IBM Launched Tasks Vendor: IBM Corporation Category: Launch File Error JAR resources in JNLP are not signed by same certificate
Explanation
This error occurs if you install the version 6.1.2 Director Server Core Manager update, but do not install the version 6.1.2 System x and BladeCenter Manager update. For all code to be signed using the newest RSA Certificate, you must install both manager updates at the same level.
Resolution
To resolve this problem, install the version 6.1.2 System x and BladeCenter Manager update, using Update manager.
Launched-tasks feature fails on System z system

This problem affects System z browser systems.
Problem
When you try to start a launched task and your browser system is a System z system, the task fails to launch.
Explanation
The launched-tasks feature in IBM Systems Director requires Java Web Start (JWS). However, JWS is not supported on System z operating systems. Therefore, the launched-tasks feature is not supported on System z operating systems.
Resolution
Change to a browser system that supports JWS and the launched-tasks feature to make sure that you have access to the complete set of IBM Systems Director functions. Operating systems that support JWS and the launched-tasks feature include all operating systems that support the IBM Systems Director Launched Tasks program. For detailed information, see Operating system support for the IBM Systems Director Launched Tasks program.
84
Message indicates a failure to validate certificate

Problem
When you try to start a launched task that uses the Java Web Start (JWS) application, a message is displayed indicating that the application will not be run due to a failure to validate the certificate published by IBM.
Explanation
This message can occur because the SSL certificate published by IBM that was used to sign files has expired and the Java security settings do not allow users to grant permission to the certificate.
Resolution
To resolve this problem, complete the following steps: 1. Start the JWS application.
Table 2. Starting JWS For Linux Type javaws at a command prompt. The javaws.exe file is located in the directory path where you installed the Java Runtime Environment (JRE). Open Control Panel and click the Java Web Start icon to start JWS.
For Windows
2. The Java Cache Viewer is displayed. 3. Click Close. The Java Control Panel is displayed. 4. Click the Advanced tab. 5. On the Advanced page, expand Security. 6. Make sure "All user to grant permissions to signed content" and "Allow user to grant permission to content from and untrusted authority" are checked. 7. Click OK. 8. Start the affected launched task again. This time a warning message is displayed stating that the applications digital signature has an error. The message will also indicate that the signature was generated with a trusted certificate published by International Business Machines, but has expired. 9. Click Always trust content from this publisher. 10. Click Run. Note: Once you have verified that the problem has been resolved, you can return your Java security settings to their original values.
Message indicates that the applications digital signature has an error

Problem
When you try to start a launched task that uses the Java Web Start (JWS) application, a message is displayed indicating that the application's digital signature has an error. The message further indicates that the digital signature was
85
generated with a trusted certificate published by IBM but has expired or is not yet valid.
Explanation
These messages can occur because the SSL certificate published by IBM that was used to sign files has expired.
Resolution
To resolve this problem, complete the following steps: 1. On the message, click Always trust content from this publisher. 2. Click Run.
Message indicates that the installation image for console cannot be found
Problem
When you try to start a launched task, a message is displayed indicating that IBM Systems Director cannot find an installation image for a console, such as IBM TotalStorage DS Storage Manager for DS4000.
Explanation
These messages can occur in the following situations: v Your browser system does not have direct access to the Internet. v You are accessing the Internet through a proxy server, but you have not configured your browser or the Java Web Start (JWS) application correctly.
Resolution
To resolve this problem, perform one of the following actions: For a browser system that uses a proxy server to access the Internet v Make sure that your browser is configured to use the proxy server. For more information, see the configuration instructions for your browser. v Configure JWS to use the proxy server by completing the following steps: Note: The name of the Java Web Start setting might be slightly different depending on the installed version of the Java Runtime Environment (JRE) and the provider. Therefore, the following instructions provide general instructions about how to configure JWS to use the proxy server. 1. Start the Java Web Start (JWS) application by running javaws at a command prompt. The javaws executable file is located in the directory path where you installed the Java Runtime Environment (JRE). 2. Navigate to the JWS network settings. 3. Make sure that the settings do not specify a direct connection. 4. Select Use browser settings if this option exists and it does not specify a direct connection.
86
Try the task again. If the same error message is displayed, continue to step 5. 5. Select Use proxy server and specify the address and port for your proxy server. For a browser system without direct access to the Internet and does not use a proxy server to access the Internet IBM Systems Director cannot automatically install the client-based consoles required to perform launched tasks. It is recommended that you configure a proxy server to access the Internet. If it is not possible for you to use a proxy server to access the Internet, contact your next level of support or your service provider. For detailed information, see Configuring Web browsers to use Java Web Start.
Message states that Java Web Start is required

Problem
When you try to start a launched task, a message is displayed indicating that Java Web Start (JWS) is required to launch the selected task.
Resolution
Java Web Start (JWS) software is required to enable the launched-tasks feature in IBM Systems Director. If the error message includes a link to a Web site, click the link to download JWS. Alternatively, complete the steps in Downloading Java Web Start in the IBM Systems Director Systems Management Guide.
Multiple Firefox browser windows open

This problem affects Firefox Web browsers.
Problem
When you try to start a launched task, multiple Firefox browser windows open.
Explanation
The .jnlp extension is incorrectly mapped to open a new Firefox browser window.
Resolution
To map the .jnlp extension to the Java Web Start executable file, complete the steps in Updating the Firefox Web browser to use the IBM Java Web Start program.
Opening launch.jnlp window is displayed

This problem affects the Mozilla Firefox browser.
Problem
When you try to start a launched task, the Opening launch.jnlp window is displayed. The message asks you what your browser should do with the file.
87
Resolution
To resolve this problem, complete one or more of the following actions: v Java Web Start (JWS) software is required to enable the launched-tasks feature in IBM Systems Director. If the error message includes a link to a Web site, click the link to download JWS. Alternatively, complete the steps in Downloading Java Web Start in the IBM Systems Director Systems Management Guide. v In the Opening launch.jnlp window, click Open with, click Browse, select the javaws executable if it exists, and click OK. Note: If the Open with option in the Opening launch.jnlp window is disabled, you must map the launch.jnlp file to JWS manually. To map the launch.jnlp file to JWS manually, complete the following steps: 1. Download a MIME type editor extension for Mozilla Firefox, such as Mime Type Editor 0.2. 2. In Mozilla Firefox, click Tools > Mimetypes. 3. In the Mimetype Editor window, perform one of the following actions: If application/x-java-jnlp-file is displayed in the file type pane, click Edit. If application/x-java-jnlp-file is not displayed in the file type field, click New Type to add it. 4. In the Edit Type window, specify the following values: MIME Type: application/x-java-jnlp-file Description: Java Web Start Extension: jnlp 5. Select Open it with:. 6. Click Choose. 7. Browse for and select the javaws executable. 8. Click OK.
Storage application launch failure information

These are problems that can occur when you launch an external storage application, along with suggested solutions.
ATKLIC012W Unable to locate application name on this system

This means that the external storage application has not been installed on your system. These applications are not automatically installed with IBM Systems Director. You must locate and install them, most likely by going to the appropriate product web page.
ATKLIC014W This task requires application name. An earlier version of application name is installed on this system, but you must install a later version of application name to complete the task. To learn about supported software versions and how to install them, click Help.
This means that an earlier version of the external storage application is on your system. You must uninstall the earlier version, then install the supported version. See the Learn More link for the supported versions and other installation information.
88
Unable to display the requested help

This problem affects the Mozilla Firefox Web browser.
Problem
When you click Help on a launched-task message to view the help text, the following message is displayed:
Unable to display the requested help. Ensure that you specify the path to your current browser in the Java Web Start settings and click Help again.
Resolution
To resolve this problem, complete the following steps: 1. Start the Java Web Start (JWS) application by running javaws at a command prompt. The javaws executable file is located in the directory path where you installed the Java Runtime Environment (JRE). 2. Make sure that you specify the path to your current browser in the JWS settings. Note: The name of the Java Web Start setting might be slightly different depending on the installed version of the Java Runtime Environment (JRE) and the provider. For example, Java Web Start might refer to this setting as a command to launch a default browser or as a browser setup path. 3. Close the message window. 4. In the original window, click Help again. For detailed information, see Configuring Web browsers to use Java Web Start.
Unable to launch the application

Problem
When you try to start a launched task, one of the following messages is displayed:
Unable to launch the application.
or
Application Error Unable to launch the application.
or
Java Web Start - Invalid Argument Error Unable to launch the specified application.
or
Java Web Start - Launch File Error Unable to launch the specified application.
or
Java Web Start - Download Error Unable to launch application
or
89
Java Web Start - Launch File Error Unable to launch application
where application is the name of the program that failed to launch.
Investigation
In the Application Error window, click Details. If the More Information window displays the following error message, the problem is caused by an unsupported version of Java Runtime Environment (JRE) and the JRE settings that do not allow IBM Systems Director to download and install the supported version of the JRE:
The application has requested a version of the JRE (version 1.5.0+) that currently is not locally installed. Java Web Start is unable to automatically download and install the requested version. This JRE must be installed manually.
If the More Information window displays the following error message, the problem is caused by the JRE settings not allowing temporary Internet files to be saved on the computer.
Cache must be enabled for nativelib or installer-desc support.
Explanation
These messages can occur in the following situations: v Your browser system does not have direct access to the Internet. v You are accessing the Internet through a proxy server, but you have not configured your browser or the Java Web Start (JWS) application correctly. v (Web browsers running on systems installed with Java version 6.0) Your browser system has an unsupported version of Java Runtime Environment (JRE) installed and the JRE settings do not allow IBM Systems Director to download and install the supported version of the JRE. IBM Systems Director supports Java version 5.0 and its JRE. v (Web browsers running on systems installed with Java version 6.0) Your JRE settings do not allow temporary Internet files to be saved on your computer.
Resolution
To resolve this problem, complete the applicable procedure: For Internet Explorer Complete the following steps: v Make sure that you have installed all software updates for the version of Internet Explorer that you are using. Use Windows Update to access software updates for Internet Explorer. v Click Tools > Internet Options > Advanced. Make sure that Do not save encrypted pages to disk is not selected. For Mozilla Firefox browser systems with a JRE installed that is earlier than version 1.4.2 Service Release 11 If you have a version of IBM JRE that is earlier than version 1.4.2 Service Release 11, you must install a later version of the JRE. In order to download required code updates, IBM Systems Director requires that the IBM JRE version be between version 1.4.2 Service Release 11 and version 5.0.
90
For a browser system with JRE version 6.0 or later installed Complete the following steps: 1. Start the Java Web Start (JWS) application.
For Linux For Windows Type javaws at a command prompt. The javaws.exe file is located in the directory path where you installed the Java Runtime Environment (JRE). Open Control Panel and click the Java Web Start icon to start JWS.
The Java Cache Viewer is displayed. 2. Click Close. The Java Control Panel is displayed. 3. Click Settings under Temporary Internet Files. 4. On the Temporary Internet Files page, select Keep temporary files on my computer. 5. Click OK. 6. 7. 8. 9. 10. Click the Advanced tab. On the Advanced page, expand JRE Auto-Download. Click Prompt User. Click OK. Start the affected launched task again. A prompt is displayed to download the required version of Java.
For a browser system that uses a proxy server to access the Internet Complete the following steps: v Make sure that your browser is configured to use the proxy server. For more information, see the configuration instructions for your browser. v Configure Java Web Start to use the proxy server by completing the following steps: Note: The name of the Java Web Start setting might be slightly different depending on the installed version of the Java Runtime Environment (JRE) and the provider. Therefore, the following instructions provide general instructions about how to configure JWS to use the proxy server. 1. Start the Java Web Start (JWS) application by running javaws at a command prompt. The javaws executable file is located in the directory path where you installed the Java Runtime Environment (JRE). 2. Navigate to the JWS network settings. 3. Make sure that the settings do not specify a direct connection. 4. Select Use browser settings if this option exists and it does not specify a direct connection. Try the task again. If the same error message is displayed, continue to step 5 on page 87. 5. Select Use proxy server and specify the address and port for your proxy server. For detailed information, see Configuring Web browsers to use Java Web Start. For a browser system without direct access to the Internet and does not use a proxy server to access the Internet IBM Systems Director cannot automatically install the client-based consoles required to perform launched tasks. It is recommended that you configure
91
a proxy server to access the Internet. If it is not possible for you to use a proxy server to access the Internet, contact your next level of support or your service provider. For detailed information, see Configuring Web browsers to use Java Web Start.
Unable to load resources

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers pointing to a Linux management server.
Problem
When you try to start a launched task, a message is displayed indicating that resources could not be loaded.
Explanation
The problem can be caused by either of the following situations: v The absence of an entry in the /etc/hosts file that maps the IP address of the server with the fully qualified host name of the server. v The presence of an entry in the /etc/hosts file for the fully qualified host name of the server that does not map to an IP address that can be used to access the management server from the browser system. For example in the /etc/hosts file, the following entry must be present:
xxx.xxx.xxx.xxx server.company.com server
where: xxx.xxx.xxx.xxx is an IP address that can used to access the server from the browser system. server.company.com is the fully qualified host name. server is the short host name. v (Management servers running SUSE Linux Enterprise Server) This problem results from the existence of an entry in the /etc/hosts file for the IP address 127.0.0.2. This entry results in IBM Systems Director identifying the IP address of the affected system as 127.0.0.2. Some IBM Systems Director functions on the affected managed system and the management server will fail to work as designed when this situation occurs. Note: Using the DNS and host name configuration function of the YAST system tool inserts a 127.0.0.2 entry into the /etc/hosts file.
Resolution
To resolve this problem, complete the following steps: 1. Complete the applicable step.
For SUSE Linux Enterprise Server In the /etc/hosts file on the affected managed system, comment out the 127.0.0.2 entry. Insert the pound sign symbol (#) in the first character position of the entry, for example: # 127.0.0.2 server.company.com server v server.company.com is the fully qualified host name. v server is the short host name.
92
For other Linux distributions
Update the final entry in the /etc/hosts file to contain the following information: v An IP address that can be used to access the management server from the browser system. v The fully qualified host name.
2. Save the /etc/hosts file. 3. Stop the management server using the smstop command. For more information, see smstop command in the IBM Systems Director Commands Reference. 4. Restart the management server using the smstart command. For more information, see smstart command in the IBM Systems Director Commands Reference. 5. Open the IBM Systems Director Web interface and start the affected launched task again.
Windows fails to open a file

This problem affects the Microsoft Internet Explorer Web browser.
Problem
When you try to start a launched task, the following message is displayed:
Windows cannot open this file:
Explanation
The .jnlp extension might not be mapped to the Java Web Start executable file.
Resolution
To map the .jnlp extension to the Java Web Start executable file, complete the procedure detailed in Updating the Microsoft Internet Explorer Web browser to use the IBM Java Web Start program in the IBM Systems Director Systems Management Guide.
Accessibility troubleshooting, including JAWS

This section provides information about problems and workarounds for accessibility and the Freedom Scientific JAWS for Windows screen reader in IBM Systems Director.
Accessible method for installing IBM Systems Director

Use unattended (silent) install to bypass accessibility limitations of InstallAnywhere.
Problem
When using the JAWS screen reader, the installation interface is not read in a meaningful order.
Resolution
This problem is a known limitation of InstallAnywhere.
93
To work around this problem, follow the procedure for Performing an unattended installation of IBM Systems Director Server on Windows. Note: Silent install does not provide result data when running. After the silent install, review the installation log file c:\windows\dirinst.log to verify successful installation or review any error messages.
Preventing session timeouts for users with disabilities

Modify the default session timeout to allow disabled users more time to complete tasks. The IBM Systems Director Server limits the amount of time a browser session can remain inactive before the session is timed out and the user is returned to the Director login screen. To reduce the risk that an abandoned browser session could be accessed by an unauthorized user, the session timeout property is set to 30 minutes by default and not recommended to exceed 20 hours. A value of -1 disables session time out altogether. This property is a global setting on the Director Server and therefore applies to all browser sessions. If disabled users need extended time to work with the interface, an administrator can customize the browser session timeout for all users using the following steps: 1. Edit the file <Director-install-directory>\lwi\conf\overrides\ usmi_settings.properties 2. Change the com.ibm.pvc.webcontainer.http.sessionGlobalTimeout property value to the wanted session timeout in minutes. Example: com.ibm.pvc.webcontainer.http.sessionGlobalTimeout=30 3. Save the usmi_settings.properties file. 4. Restart the Director Server for the changes to take effect. Note: This action interrupts all active browser sessions.
Audible notification is not supported in Internet Explorer

This problem exists in the IBM Systems Director Web interface.
Problem
The Play sound when data on the page changes option is enabled option in the Navigation Preferences window is supported only by Firefox. It does not correctly play an audible notification when using Internet Explorer.
Resolution
This problem is a known limitation of IBM Systems Director 6.1.
Audible notification is not given after a dynamic refresh completes

This problem exists in the Error Counters page in the IBM Systems Director Web interface.
Problem
The Error Counters page contains a set of resources and the View Error Counters and Refresh Error Counters buttons. Clicking these buttons starts a dynamic process that populates or refreshes the error counters table. IBM Systems Director fails create an audible sound to notify you when the refresh has completed, even
94
though the Play sound when data on the page changes option is enabled in the Navigation Preferences window.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To work around this problem, wait a few minutes and then manually read the table to see if it is populated or has changed.
Audible notification is not given after a manual refresh completes

(IBM Systems Director 6.1 only) This problem exists in the Storage Resources page in the IBM Systems Director Web interface. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
The Storage Resource page contains several tabs, each displaying a nested table with a Refresh button. Clicking this button refreshes the data in the table. IBM Systems Director fails create an audible sound to notify you when the refresh has completed, even though the Play sound when data on the page changes option is enabled in the Navigation Preferences window.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To work around this problem, wait a few minutes and then manually read the table to see if it has changed.
Audible notification is not given after changing the page

This problem exists in the Virtualization Manager in the IBM Systems Director Web interface.
Problem
IBM Systems Director fails create an audible sound to notify you when you change pages from the Virtualization Manager Edit Virtual Server and Edit Host pages, even though the Play sound when data on the page changes option is enabled in the Navigation Preferences window.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To work around this problem, when using the JAWS screen reader, listen for a verbal indication that the page has changed. JAWS repeats the name of the page after you press the Tab key to go to that page.
Create Virtual Server wizard displays previous page when pressing Enter in a text field
This problem exists in the Create Virtual Server wizard in the IBM Systems Director Web interface.
95
Problem
In the Create Virtual Server wizard, when you type data in an entry field and then press Enter, the wizard displays to the previous page.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To resolve this problem, tab to Next at the bottom of that page and press Enter. Then, tab to Next and press Enter again to move to the next page. To avoid this problem, type the data in the text field, and then tab to Next at the bottom of the page and press Enter.
Cursor disappears and page refreshes when performing virtualization manager tasks
This problem affects the IBM Systems Director Web interface when you perform virtualization manager tasks.
Problem
When you perform tasks such as Create Virtual Server, Edit Virtual Server, or Edit Host, the page refreshes and the cursor seems to disappear. For example, to perform a task you might select a row in a table, select a radio button, or browse to select an item in a list. When you select the row, select a radio button, or browse through the list, the page refreshes and the cursor seems to disappear. The cursor actually moves to the address bar at the top of the browser window; however, you might not be able to see the cursor. Consequently, you must manually move the cursor back to the page to complete the task.
Resolution
You can use a mouse to click on the page to complete the task. If you are unable to use a mouse, you must press Tab to return to the page to complete the task. To prevent this problem from occurring in a list, you can browse and select the list item by pressing Alt and the Down Arrow key.
Focus is lost when clicking the Select All or Deselect All button
This problem exists in virtualization manager the IBM Systems Director Web interface.
Problem
Clicking the Select All or Deselect All button might cause the page to refresh, which results in a loss of focus on the current field position on the page. This occurs in the Edit Virtual Resources page.
96
Resolution
When the page refreshes, focus moves to the top of the page. Navigate back to the desired location on the page.
Identifying table filter row information using JAWS

This problem exists in the IBM Systems Director Web interface. The table summary identifier shown when issuing a list tables command in JAWS with table filter row enabled shows two tables with similar summaries.
Problem
One of the features of the tables used in the IBM Systems Director Web interface is to allow for filtering of the data contained in the rows of a given table. The feature is enabled by selecting Show filter row in the Action menu. When using JAWS to list the tables on a page after enabling the filter row functionality, two tables are listed with similar tables summaries. The table identified as having two rows after enabling filter row capability is the filter control table for the main table.
Examples
If you select the Navigate Resources link in the console navigation and then select the All Operating Systems resources link, if you issue the JAWS list tables command, the JAWS dialog lists one table with the summary "This table contains the resources found in the 'All Operating Systems' data set 9x6". If you select Show filter row from the Actions button menu and then issue the JAWS show all tables command, JAWS lists the two tables on the page, one with the previous summary, and another with the summary "This table contains the resources found in the 'All Operating Systems' data set 9x2". This second two-row table contains the filter row control for the first table and can be used to define filters to filter the data in the main table.
Resolution
Use the second table which contains the filter row control to filter the main table.
JAWS screen reader becomes mute

This problem exists only in the Create Simple Event Filter page in the IBM Systems Director Web interface.
Problem
When using the JAWS screen reader with the Java Access Bridge and the Java Console, if you clear the Any check box in the Event Type page, JAWS becomes mute and several keys on the keyboard are frozen, which causes the Web interface to become unusable.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To recover, close and then restart JAWS and the IBM Systems Director Web interface, but do not reattempt the above function
97
JAWS does not read Pre-Installation Utility content

This problem exists in the IBM Systems Director Pre-Installation Utility.
Problem
When using the IBM Systems Director Pre-Installation Utility to install IBM Systems Director with JAWS screen reader, the frames are read but the page content is not read by the screen reader.
Resolution
This problem is a known limitation when using older versions of JAWS. To work around this problem, install JAWS version 11.0.1471 or later. Note: If you use the Pre-Install Utility to start installation of IBM Systems Director, the JAWS screen reader does not read the installation interface in a meaningful order. See related topic Accessible method for installing IBM Systems Director for more information.
JAWS screen reader reads extra frame

Problem
In the Remote Command Line page, if you request the list of frames in the page and then navigate to frames in the list using the M key, the screen reader reads the extra viewns frame at the end of the list. This also happens when using the Window Eyes screen reader.
Resolution
Ignore the extra viewns frame when it is read.
JAWS cannot read remote serial console output

This problem inhibits use of Remote Access Serial Console with JAWS.
Problem
If you select a CEC server and launch the Remote Access Serial Console, JAWS cannot read the console content. An alternate method of access is required to enable JAWS.
Resolution
To work with remote serial functions with JAWS, use the following steps: 1. Open a Windows command prompt window and Telnet to the management server (the server running IBM Systems Director Server). 2. From the management server command line, type export DISPLAY=window. 3. From the management server command line, type the smcli dconsole command with the -v option, for example:
smcli dconsole -n julie04 -v
The output should look similar to this:
98
LPAR STANZA constructed: julie04|hmc|9.3.149.181|TargetHWTypeModel=9117-570: TargetHWSerialNum=109DB9D:TargetLPARID=4|/tmp/dc_pw/dp Launching console /tmp/dconsole_router julie04|hmc|9.3.149.181| TargetHWTypeModel=9117-570:TargetHWSerialNum=109DB9D:TargetLPARID=4|/tmp/ dc_pw/dpwith DISPLAY=window julie04: Launching serial console window
4. From the management server command line, type the dconsole command with the -t option and the STANZA from the previous step, for example:
dconsole -t -n julie04|hmc|9.3.149.181|TargetHWTypeModel=9117-570: TargetHWSerialNum=109DB9D:TargetLPARID=4|/tmp/dc_pw/dp
5. The Windows command prompt window should become the remote console to the specified target in the previous step. JAWS can read the input and output generated in the Windows command prompt window.
JAWS screen reader reads some Web interface elements incorrectly

Problem
When using the JAWS screen reader the following Web interface elements might not be read correctly in Firefox. v As you navigate from one resource to another or drill down from a resource to its subcomponents, a breadcrumb path is displayed at the top of the page as a navigational signpost. The breadcrumb link for the current page might be read incorrectly. v Required fields in the Console Logging and Tracing page might not be read correctly. v Submenus in the Actions menu are incorrectly identified as links. v If the Show Filter Row action is enabled in a table and you press Ctrl-Alt-RightArrow to read the filter row, the filter row is not read correctly, even if the Enable tables for accessibility option is enabled in the Navigation Preferences window. Instead, the Name column in the header row is read repeatedly. v The radio button group text in the Create Virtual Server Image page is not being read, but the radio button descriptions are being read correctly. v The Browse button on the Import Groups page is not read correctly. v At the end of labels, "..." might be read. This means that there is another window or panel open to which you can navigate. v In the Create Virtual Farm and Create Relocation Plan wizards, the Status icons that indicate previous and future steps might not be read correctly. As you navigate to each step in the wizard, the name of the current step is read correctly. v The label of the icon before an error message is not read, even if the Enable tables for accessibility option is enabled in the Navigation Preferences window. The error message is read correctly. v When you click on links to the summary pages from the Welcome - Manage page, a new page is displayed. When using the JAWS screen reader, links on the to the summary pages are read as if the summary pages are in the same page. v Hidden frames with their invisible elements (such as invisible buttons) are being read. For example, if multiple tabs are open, only the current tab is visible in the browser, but JAWs reads the inactive tabs as well as the active tab.
99
Another example is in Disk Selection page in the Create Virtual Server wizard. Frames that are intended to be hidden, and therefore do not have label descriptions, are being read.
Resolution
These problems are a known limitations of IBM Systems Director 6.2. You can use the following workarounds for some of these problems: v To correctly read the filter row, navigate through the cells in the filter row using the Tab key.. v When you encounter the radio button group in the Create Virtual Server Image page, force the JAWS screen reader to read the entire page, which will include the radio button group text.
JAWS screen reader suggests incorrect keys for radio buttons in a table
This problem exists in the IBM Systems Director Web interface. JAWS may, depending on settings, incorrectly direct you to use the arrow keys to change radio button selection for radio buttons embedded in a table.
Problem
When using the JAWS screen reader, depending on the verbosity setting, JAWS may direct the user to use the arrow keys to change the state of radio buttons embedded in certain tables for table row selection, but the arrow keys do not work to change the state of the radio button. Use the enter key or space key (depending on their JAWS Keyboard Manager settings) to change the state of such a selected radio button.
Resolution
Use the space bar or enter key to change the radio button selection state instead of the arrow keys as possibly directed by Director.
JAWS screen reader reads the Next button incorrectly on some pages
Problem
When using IBM Systems Director wizards in Internet Explorer, if you enter data in a text field (in other words, if you type data and then press Enter), the Next button might not be enabled correctly to advance to the next page. Note: This works correctly using Firefox.
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To work around this problem, manually tab to Next at the bottom of the wizard then press Enter to advance to the next panel.
100
Keyboard navigation does not work in or between Selected and Available list boxes
This problem exists in virtualization manager the IBM Systems Director Web interface.
Problem
When using the JAWS screen reader you might experience the following problems: v The JAWS Tab or F key does not read the text above the Available list box. This problem occurs when creating templates or selecting multiple objects before submitting a task. v Keyboard navigation does not work when moving from Selected list box back to the Available list box after removing items from the Selected list box in the Disk Selection page of the Create Virtual Server wizard. The focus goes to the Add button instead of the Available list box.
Resolution
To work around these problems: v To read the text above the Available list box, use the arrow keys instead of The JAWS Tab or F key. Note that using the arrow keys, JAWS reads text that explains how the dialog works. v After the focus goes to the Add button, press Shift-Tab to put focus on the Available list.
Keyboard navigation does not work in some Action menus

Problem
When using the JAWS screen reader, the Actions menu cannot be traversed using arrow keys keyboard in the Create Virtual Server wizard - Disk Selection page and the File Transfer page.
Resolution
Perform these steps to work around this problem: 1. Bring focus to the Action menu by tabbing to the Actions menu. Do not use the B or F hot keys. 2. Press Shift+space bar to open the table Actions menu. 3. Press Ctrl+Shift+down arrow to select an action in the Actions menu. 4. Press Shift+Enter to run the selected action.
Language attribute not set properly in some panels when using Internet Explorer
Problem
The LANG attribute of the HTML element determines which language assistive technologies, such as Braille software and screen readers, to use to correctly pronounce the text. The LANG attribute is set properly when using the Firefox, but
101
it is not set correctly in some pages when using the Internet Explorer.
The calendar is not usable or readable by the JAWS screen reader in forms mode
This problem affects the Run window in the IBM Systems Director Web interface.
Problem
In the Run window, on the Schedule page, the calendar is not usable or readable by the JAWS screen reader in forms mode with any supported Web browser.
Resolution
To resolve this problem, complete the following steps: 1. Navigate to the Date field. 2. Type the desired date using the format mm dd, yyyy, where: v mm is the name of the month v dd is the two-digit day of the month v yyyy is the four-digit year 3. Force the screen reader to read the content.
The Time field is not readable by the JAWS screen reader

This problem affects the Run window in the IBM Systems Director Web interface.
Problem
In the Run window, on its Schedule page, the Time field is not readable by the JAWS screen reader with any supported Web browser.
Resolution
To resolve this problem, complete the following steps: 1. Navigate to the Time field 2. Type the desired time using the format hh:mm, where hh is the hour and mm is the minutes. 3. Force the screen reader to read the content.
Unable to navigate to expanded content with traditional key sequences when using JAWS screen reader
(IBM Systems Director 6.1 only) This problem exists in the RSSM/NSSM Ports panel in the IBM Systems Director Web interface. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
When using the JAWS screen reader, the traditional JAWS key sequences do not navigate to the expanded content in the Blade Bay Ports and External SAS Ports sections on the RSSM/NSSM Ports panel. JAWS does not say the names of check boxes and associated text when using the Tab key, forms keystrokes or Insert+down arrow keys to reach this area.
102
Resolution
This problem is a known limitation of IBM Systems Director 6.1. To work around this problem, use the Insert+left arrow and Insert+right arrow key combinations to read one word at a time.
Unable to select table row using JAWS screen reader in Internet Explorer
This problem exists in the virtualization manager in the IBM Systems Director Web interface.
Problem
When using the Create Virtual Server, Edit Virtual Server or Edit Host page while using the JAWS screen reader within the Internet Explorer browser, you cannot select a row in the table using the space bar. Normally, you can select or clear a row by tabbing to the selection column in the row and then pressing the space bar.
Resolution
To work around this problem: v Use the Firefox browser. Rows can be selected using the space bar in this browser. v If using Internet Explorer, you can select a row in the following manner: 1. Press T to start browsing the table using the Ctrl+Alt+arrow keys. 2. Browse to any given check box or radio button under the Select column and press Ctrl+Insert+Del to set focus on the selection component. 3. After focus has been set, press Shift+space bar to select or clear the check box or radio button.
Automation manager troubleshooting

This section provides information about problems and workarounds for the automation manager plug-in.
A program fails to run when the event automation plans is triggered

This problem affects event automation plans that include either of the following event actions: Start a program on a system or Start a program on the system that generated the event.
Problem
When creating either of the following event actions, you specify a program to run when the event action is invoked: v Start a program on a system v Start a program on the system that generated the event However, the program might not run after the event occurs that triggers this action.
103
Explanation
These two types of the event actions are used to run a program to complete some systems-management tasks on a remote system when an event occurs. However, the program must be an executable and IBM Systems Director must be able to access and manage the affected system.
Resolution
To resolve this problem, complete the following steps: 1. If the event action history was activated, check to make sure the event action was launched. For more information, see Activating and deactivating an event-action history and Viewing an event-action history. 2. Make sure the selected protocol for the event action is correct. If the specified system is running Common Agent, the selected protocol must be CAS. If the specified system is running IBM Director Agent version 5.20, the selected protocol can be TCP/IP, IPX, or NETBIOS. 3. Make sure that the program is an executable. 4. The system specified in the action must be running either IBM Systems Director Server or Common Agent. Also, IBM Systems Director Server must be able to access Common Agent. If not, request access to the system. For more information, see Requesting access to a secured system. 5. On system specified, make sure that the com.ibm.usmi.client.ipc_1.0.0 plug-in was installed successfully in the install_root/agent/runtime/agent/subagents/ eclipse/plugins/ directory where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
Active Energy Manager threshold options are not displayed in the Event Automation Plan wizard
This problem affects the Event Automation Plan wizard after you have installed the Active Energy Manager plug-in.
Problem
After you install the Active Energy Manager plug-in, additional threshold options should become available in the Event Automation Plan wizard; however, they do not.
Explanation
The Active Energy Manager license has expired or the Active Energy Manager plug-in is not installing correctly.
Resolution
Check the license agreement and make sure that the Active Energy Manager plug-in was installed successfully.
The specified event does not trigger the event automation plan
This problem affects event automation plans.
104
Problem
An event automation plan specifies an event for monitoring. However, when the event occurs the event automation plan is not triggered.
Explanation
This problem can be due to either of the following situations: v The event automation plan is deactivated. v The event filter no longer exists.
Investigation
Make sure that the event automation plan is activated. On the Event Automation Plans page, view the Status column to see if the plan is Active or Inactive. Make sure that the event automation plan has an associated event filter displayed on the Event Filters page. Note: If the event automation plan was created using the Event Automation Plan wizard and you selected a common event filter, the filter name is plan_name-Filter, where plan_name is the event automation plan name. If the event filter is not displayed, it no longer exists.
Resolution
To resolve the problem, complete the following applicable steps: Deactivated event automation plan 1. On the Event Automation Plans page, select the affected event automation plan. 2. Click Actions > Activate. Missing event filter 1. On the Event Automation Plans page, select the affected event automation plan and click Edit. 2. In the Event Automation Plan wizard, click Events in the left pane. 3. On the Events page, update the event automation plan to contain the event. Note: If Common was selected in the Events list, editing the event automation plan recreates the event filter that was originally specified. 4. Click Summary in the left pane. 5. On the Summary page, click Finish.
An event automation plan is not triggered when the event filter uses extended details
This problem affects event automation plans that include an event filter that uses extended details. While this problem can affect any event filter that uses extended details, this resolution provides information that is specific to message events from IBM i systems.
105
Problem
An event automation plan with an event filter that uses extended details might not trigger as expected. Many individual event types have extended details. For more information about extended details, see the IBM Systems Director Events Reference.
Investigation
IBM i message events, like other event types, have extended details that are specific to the event type. The keywords to operate on are listed but the values that are applicable to those keywords are usually not listed. The values can be found external to IBM Systems Director. Make sure that the logical OR and logical AND (as described in the help) that apply to the selected keyword or keywords works for the intended inclusion or exclusion of the event.
Explanation
Values for extended details are found outside IBM Systems Director. Event filters using extended details that have multiple values for the same keyword use logical OR, but multiple keywords use logical AND.
Resolution
To avoid having an event automation plan fail to trigger after changing the event filter with extended details, make sure the logic for the filtering of events is correct in the following situations: v When using logical OR on multiple values of the same keyword v When using logical AND on multiple keywords
IBM i message events have several keywords listed such as Message type and Message severity. The following table lists the possible values and meanings for the Message type keyword.
Table 3. Possible values and meanings for the Message type keyword Value 01 02 04 05 06 08 10 14 15 16 17 21 Message Type Completion Diagnostic Informational Inquiry Sender's copy Request Request with prompting Notify, exception already handled Escape, exception already handled Notify, exception not handled Escape, exception not handled Reply, not checked for validity
106
Table 3. Possible values and meanings for the Message type keyword (continued) Value 22 23 24 25 26 Message Type Reply, checked for validity Reply, message default used Reply, system default used Reply, from system reply list Reply, from exit program
The Message severity is the value of the severity code which is a number from 0 to 99. The Message severity is much like the severity of a message on the Severity page in the Event Filter Builder window, except on the Severity page the severity is a mapping of the number to a keyword. Severity IBM Systems Director maps the message event severity as follows if msg severity < 10 then HARMLESS else msg severity < 20 then WARNING else msg severity < 30 then MINOR else msg severity < 80 then CRITICAL else msg severity is FATAL
An SNMP trap or an SNMP inform request was not received

This problem affects event automation plans that include any of the following event actions: Send an SNMP INFORM request to an IP host, Send an SNMP trap reliably to a NetView host or Send an SNMP trap to an IP host.
Problem
When using any of the following event actions, the trap or the inform is not received by the SNMP program: v Send an SNMP INFORM request to an IP host v Send an SNMP trap reliably to a NetView host v Send an SNMP trap to an IP host
Explanation
These types of the event actions are used to send an SNMP trap or SNMP inform to an SNMP program. SNMP notifications can be sent out as a trap or an inform request. Traps are unreliable notification because the receiver does not reply to the sender after it receives the traps. However, the inform requests are reliable because the receiver sends an acknowledgement to the sender after receiving the inform request. To receive SNMP traps or inform requests, the SNMP program must be configured correctly. Note: An SNMP program that can receive traps does not mean that it can receive inform requests.
Resolution
Configure the SNMP program correctly. For more information, see the SNMP program documentation.
107
Note: There is no configuration required for IBM Systems Director Server to send an SNMP trap or inform request.
Automation plan not activated for virtual farm or relocation event

This problem can affect several virtualization environments.
Problem
An automation plan that uses a virtual farm event filter or relocation event filter does not get activated as expected when the specified event occurs and displays in the event log.
Explanation
You might be experiencing one of the following problems: v The Event Filter Builder displays two paths for selecting similar event types. The two paths are associated with different virtualization environments. You might be experiencing a problem with your automation plan if you have specified an event type path that is not associated with the virtualization environment where the event is occurring. v You might not have applied the automation plan to a valid target system for the event type that you plan to filter.
Resolution
Ensure that the event type that you have specified in your automation plan uses the appropriate path for your specific virtualization environment. The following table displays the paths to specify for event types in different virtualization environments.
108
Category
Path in Event Filter Builder
Event Types v A virtual farm has been created. v A virtual farm has been deleted. v A virtual farm has been renamed. v A host was added to a virtual farm. v A host was removed from a virtual farm. v Virtual farm created v Host added to virtual farm v Host removed from virtual farm v Virtual farm renamed
VMware VirtualCenter X
VMware ESX Server
Microsoft Virtual Server
HMC or IVM
Xen
Virtual farm Managed filters Resource > Managed System Resource > Logical Resource > System > Administration Domain > Farm > Life Cycle Managed Resource > Managed System Resource > Logical Resource > System > Administration Domain > Farm > Virtual Farm Events Relocation filters
Managed v Virtual server Resource > relocation has been Managed initiated for {0}. System v Virtual server Resource > relocation has Logical completed. Resource > System > Computer System > Server > Relocation Managed v Virtual server Resource > relocation started Managed v Virtual Server System relocation failed Resource > v Virtual server Logical relocation complete Resource > System > Administration Domain > Farm > Relocation Manager Events
Additionally, when you configure an automation plan for virtual farm events, ensure that you select a host that is a virtual farm member as the target system for the automation plan. For relocation events, ensure that you select the target host for relocation as the target system for the automation plan.
109
Cannot run Collect Inventory task using an event action

(IBM Systems Director 6.1 only) This problem affects the event action Start a task on the system that generated the event. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
When you create a Start a task on the system that generated the event event action and select to start the Collect Inventory task, the task fails to run when the event action is invoked.
Explanation
The Collect Inventory task provided in the Start a task on the system that generated the event event action window does not work in IBM Systems Director 6.1.
Resolution
To resolve this problem, use the event action Start a task on a specified system to invoke the Collect Inventory task.
Difficulty accessing event automation plan system variables

This problem affects an event automation plan that specifies the Set an event system variable event action.
Problem
When using the Set an event system variable event action, the system variable is not accessible from scripts and other system tools.
Investigation
The Set an event system variable event action is used to set the value of a user-defined variable. After the action is invoked, the variable and its value are not visible as operating-system environment variables. Note: The Set an event system variable event action is used to set the value of a user-defined event system variable, not operating-system variables.
Explanation
The system variables used by the Set an event system variable event action are intended for use only in event automation plans. The variables and their values can be used only in an advanced event filter to further refine the conditions for that filter. When creating an advanced event filter, in the Event Filter Builder, view the System Variables page. On this page you can specify the values of the system variables.
E-mail fails to be sent

This problem affects event automation plans that include either of the following event actions: Send an e-mail to a mobile phone or Send an e-mail (Internet SMTP) .
110
Problem
When using either of the following event actions, the e-mail fails to be sent: v Send an e-mail to a mobile phone v Send an e-mail (Internet SMTP) When you test these actions, you might receive the error message Action launch failed.
Explanation
These actions only work when the management server can reach the SMTP server.
Resolution
To resolve this problem, complete one or more of the following steps: v Verify that the SMTP server and port information is correct. v Make sure that the management server can reach the SMTP server. For example, if your firewall does not stop ICMP traffic, ping the SMTP server from the management server. If the ping fails, a connection issue exists between the management server and the SMTP server. If ICMP traffic is disabled, consider using ssh or Telnet to confirm that the servers can communicate successfully. v If applicable, check your firewall settings and access. Consider checking other network-related settings, too.
Event actions fail

This problem affects event actions.
Problem
After a network interface card (NIC) in the management server is reconfigured, certain event actions fail.
Explanation
IBM Systems Director Server has lost contact with the resources that were discovered before the configuration change.
Resolution
To resolve this problem, you must rediscover the affected resources. In the Web interface navigation pane, expand Inventory and click System Discovery. For more information, see Performing a system discovery.
Target systems are lost when an event automation plan is imported

This problem affects all hardware and operating system platforms.
Problem
You export an event automation plan from one IBM Systems Director management server (the server running IBM Systems Director Server) and import the event automation plan to a different management server. When you open the imported
111
event automation plan, the target systems are missing in the event automation plan.
Explanation
This behavior occurs when an event automation plan is exported from one IBM Systems Director management server and imported on a different management server. This behavior also occurs when using earlier versions of IBM Director. This is working as designed. Previously, each target system had an object ID (OID) generated by the management server. It was possible that two management servers could generate the same OID, but for two different systems. In that case, the imported target OID would be for a different target system than on the exporting management server. To address this, IBM Systems Director was changed to generate a globally unique ID (GUID). The GUID lets the import code detect whether the exported target systems match GUIDs on the import management server. If there is no match, there is no guarantee that the imported target systems are the same across both management servers. In this case, the target systems are deleted from the imported plan. If the deletion is not done, the imported plan could erroneously be applied to a different set of target systems than you originally specified.
Resolution
After the event automation plan has been imported onto a different IBM Systems Director management server, edit the event automation plan and select the desired target systems as they are known to the import management server.
Event automation plans are not displayed

This problem affects viewing event automation plans that affect a system.
Problem
When you view the Applied Activities page in the Properties view, one or more event automation plans that affect the selected system are not displayed.
Explanation
When you apply an event automation plan to a group, the event automation plan is associated with all existing systems in the group. However, this group event automation plan is not displayed as associated with each individual system that is a member of the group. The event automation plan is displayed as being applied to the group only.
Resolution
In order to determine whether a group-applied event automation plan affects an individual system, you must know to what groups a system belongs. While you can navigate to a group and view its members in the IBM Systems Director Web interface, you cannot view a resource and determine of what groups it is a member. Instead, use the command-line interface to determine this information: 1. Use the lsgrp command to view all groups and their members. The output is easy to scan for a specific system. For more information, see lsgp command.
112
2. Use the lsevtautopln -l command to view all event automation plans and the target systems to which they are applied. Again, the output is easy to scan for a specific system. For more information, see lsevtautopln command.
Event automation plans do not support some features of earlier event action plans
An event automation plan might not provide the same features as an event action plan that was used in IBM Director version 5.20 or earlier.
Problem
Multiple event filters and event actions that were used in an event action plan might not be permitted in an event automation plan if the event filters are Advanced event filters or the event actions are not applicable to the IBM Systems Director Web interface.
Investigation
In earlier releases, event action plans could use multiple event filters and multiple event actions. In an event automation plan, only one event filter is supported, the event filter can be one advanced event filter or one common filter for the plan that contains one or more event types. Some event actions from earlier releases are no longer available.
Explanation
The event action plans used in the past might require multiple event automation plans to provide the same coverage and the event actions might need to be different.
Resolution
When needed, create multiple event automation plans to cover all the advanced event filters that were in an event action plan. If the event action used in an event action plan no longer exists, choose a different action for your event automation plans.
Event automation plans do not work correctly

This problem affects event automation plans that reside on management servers running Windows.
Problem
Event automation plans do not work or have unpredictable results.
Explanation
Daylight savings time can affect event automation plans on days when daylight savings time starts or ends. On days when daylight savings time starts, event automation plans that are scheduled during the hour when the management server clock skips forward might not run. On days when daylight savings time ends, event automation plans that are scheduled during the hour before the management server clock falls back might run twice.
113
Resolution
To prevent this problem, do not schedule event automation plans during these times if you are in a locality that observes daylight savings time.
Event not forwarded to Tivoli Enterprise Console event server

This problem affects the event action that forwards events from IBM Systems Director Server to a Tivoli Enterprise Console event server.
Problem
The event action called Send a Tivoli Enterprise Console event does not forward some events successfully to a Tivoli Enterprise Console event server.
Explanation
When a detected event triggers the event action called Send a Tivoli Enterprise Console event, IBM Systems Director retrieves data from the incoming event and creates a packet of data to forward (transmit). The packet of data includes the system name (as it appears in the IBM Systems Director Web interface) that initiated the event. When the system name includes a pound (#) character or exclamation point (!) character, Tivoli Enterprise Console event server rejects the transmission.
Resolution
Rename the system associated with the forwarded event to remove any pound (#) characters or exclamation point (!) characters.
Group members are not processed correctly in static groups

This problem affects event automation plans that include either of the following event actions: Static group: add or remove the event-generating system or Static group: add or remove group members.
Problem
When creating either of the following event actions, the members are not added to the target group or removed from the target group, as applicable: v Static group: add or remove the event-generating system v Static group: add or remove group members
Explanation
These two event actions are used to process static groups only. Therefore, both the source group and the target group must be static groups. The members of the static group must be managed systems and the member cannot be a nested group itself.
Resolution
Make sure that the source group and target group are static groups. Also, make sure that the members in the source group are managed systems.
114
IBM i message queue events do not trigger event automation plans as expected
This problem affects event automation plans that include an event filter for IBM i message queue events.
Problem
An event automation plan does not deliver the expected results for IBM i message queue events.
Investigation
By default, IBM i message queue events are not included in the Event Filter Builder. For IBM i message queue events to be filtered, you must specify them explicitly.
Explanation
If you have configured your event automation plan to trigger IBM i message queue events, complete the following steps to verify that the event automation plan is configured correctly. 1. Make sure you have configured the event automation plan according to the instructions in Monitoring for IBM i message queue events in the IBM Systems Director Systems Management Guide. Verify that you have included each message queue event that you want to monitor and that the spelling and syntax is correct. 2. If you are using the exclusion event filter, verify that message queue events are not inadvertently being excluded, for example, if the Any field is selected. 3. Verify that any other settings that are specified in the event filter will work together with the event type that you have specified for message queue events. All criteria specified in the event filter must be met before the event action is invoked. 4. Check that the event automation plan is applied correctly to the systems that you want to monitor. 5. Make sure that any firewall configuration allows access in and out of the systems that you are monitoring. 6. Test the event automation plan to make sure that it is working as planned. a. Cause the message to be sent to the system that IBM Systems Director is monitoring with the event automation plan that you have applied. For example, you can create a CL program and use QSYS/SNDPGMMSG in the CL program to send a message to the managed system. For more information, see Commands used to send messages from a CL program. b. Manually verify that the message arrived at the message queue on the managed system by using the QSYS/DSPMSG command.
Resolution
Verify that the following items as described in the Investigation section are configured and working correctly: v The event automation plan is configured correctly for specific IBM i message queue events. v The event automation plan is applied correctly to the IBM i managed systems that you want to monitor.
115
v Communication to the managed system is possible. v The message or messages specified in the event automation plan are confirmed to arrive in the message queue on the managed system. When all items have been verified, the event automation plan should filter a message queue event and invoke an event action as described in the plan. If problems persist, contact your IBM service representative. Related information Commands used to send messages from a CL program
News fails to post to a newsgroup

This problem affects event automation plans that include the Post to a newsgroup (NNTP) event action.
Problem
When using the Post to a newsgroup (NNTP) event action, the news was not posted on the news server.
Explanation
This action can only send news to a newsgroup that does not require user login.
Resolution
Make sure that the newsgroup does not require a user login.
Resource-monitor threshold settings change unexpectedly

This problem affects event automation plans that use resource-monitor threshold settings.
Problem
A resource-monitor threshold setting that you specified in an event automation plan, changed from the value you specified unexpectedly. When the value is changed, unexpected behavior can occur in the event automation plan.
Explanation
Only one instance of a given resource monitor on a given system can be used at any time. For example, consider the following scenario: v On Monday, you create event automation plan 1 with the following resource-monitor threshold setting: Processor (CPU) resource threshold at 80% on moonlite v On Tuesday, you create event automation plan 2 with the following resource-monitor threshold setting: Processor (CPU) resource threshold at 90% on moonlite The Processor (CPU) resource threshold setting in event automation plan 1 is changed to 90%. When working with resource-monitors and event automation plans, remember the following considerations:
116
v For a given system, you can have only one resource monitor at a time for a specific resource. For example, if you want to monitor the Processor (CPU) resource on a system called moonlite, you can set a threshold for 90% in your first event automation plan. You cannot have second event automation plan that monitors the Processor (CPU) resource threshold at 80% on moonlite. If you do create another event automation plan with a different threshold setting, then that setting is also used in the first event automation plan and any other event automation plans that monitor the Processor (CPU) resource on moonlite. v For a given system, you can monitor more than one type of resource. For example, you can have one event automation plan that monitors the Processor (CPU) resource threshold at 80% on moonlite and another event automation plan that monitors the Disk resource threshold of 70% on moonlite. v You can combine more than one resource monitor threshold setting in an event automation plan as long as the resources being monitored are different. For example, you can specify the following resource-monitor thresholds in one event automation plan: The Processor (CPU) resource threshold at 80% on moonlite The Disk resource threshold of 70% on moonlite
SNMP traps do not contain message text

Problem
SNMP traps received from Platform Agent, Common Agent, or IBM Director Core Services version 5.20 do not contain message text in the events.
Explanation
This problem occurs because agent MIB files are not loaded by default on IBM Systems Director Server.
Resolution
Load the following MIB files into memory in order: 1. IBM-SYSTEM-MIB.mib 2. IBM-SYSTEM-TRAP-MIB.mib 3. Optional: Other MIB files, including the following: v IBM-SYSTEM-AGENT-MIB.mib v IBM-SYSTEM-ASSETID-MIB.mib v IBM-SYSTEM-HEALTH-MIB.mib v IBM-SYSTEM-LMSENSOR-MIB.mib v IBM-SYSTEM-MEMORY-MIB.mib v v v v v v IBM-SYSTEM-NETWORK-MIB.mib IBM-SYSTEM-POWER-MIB.mib IBM-SYSTEM-PROCESSOR-MIB.mib IBM-SYSTEM-RAID-MIB.mib IBM-SYSTEM-SMART-MIB.mib IBM-SYSTEM-STORAGE-MIB.mib
These MIB files are located in the following directory: v AIX or Linux: /opt/ibm/icc/proddata/snmp
117
v Windows: \Program Files\Common Files\IBM\icc\proddata\snmp
Start a program on a system event action fails

This problems affects event automation plans that include the Start a program on a system event action.
Problem
When an event automation plan invokes the Start a program on a system event action, the event action completion status is reported as Failed.
Explanation
This failure might be due to selecting an incorrect protocol when creating the event action. IBM Systems Director 6.1 or later supports the following managed systems: v IBM Systems Director Server 6.1 or later and Common Agent v IBM Director Server, version 5.20 and IBM Director Agent, version 5.20 IBM Systems Director 6.1 or later uses Tivoli Common Agent Services (CAS) to communicate between the management server and managed systems. IBM Director, version 5.20, uses TCP/IP to communicate between management server and managed systems. Because the protocols used for communication are changed, you must select a different protocol when creating the Start a program on a system event action, depending on the product versions that are installed on the affected management server and managed systems.
Resolution
When you create a Start a program on a system event action, select the applicable protocol depending on the version of the product installed on the target system.
Product version installed on the target system Protocol to select
IBM Systems Director Server 6.1 or later, and CAS Common Agent IBM Director Server 5.20, and IBM Director Agent 5.20 TCP/IP
Test results are missing for an event action

This problem can affect any event action that you have tested.
Problem
When an event action is created, it is a best practice recommendation that you test the action before using it in an event automation plan. However, when you do test the action you cannot find a record of the test results.
Explanation
The success or failure of an event action is recorded in the event-action history. By default, the event-action history for each action is disabled. You can enable the
118
history either on the Event Actions page or using the command-line interface. The History column in the table on the Event Actions page indicates whether the history is enabled for each action. If the history is disabled, you can enable it by selecting the action and then clicking Actions > Enable History. After the event-action history is enabled for an action, the results of that action are logged when it is invoked from an event automation plan or when you test the action from the Event Actions page. Note: If you test an action from the Event Automation Plan wizard, the results of that test are not recorded because, by default, that action's history is disabled. The event-action history reports when an action is invoked and when it completes. Important: The successful launch of an action does not imply that the action also completed successfully. Also, when creating or editing certain types of event actions, a Test button is available to test the action. The testing of the action in the Create or Edit window does not capture the test result, it only indicates whether the event action was launched successfully. To verify that the action successfully completed, you must check the action's outcome. For example, if you created an e-mail action, check your e-mail to see if you received your test e-mail.
Resolution
Enable the event-action history for an event action before testing the action. Select the action and then click Actions > Enable History.
Threshold values are no longer selected or are zeroed out in an event automation plan
This problem affects event automation plans that were created in the Event Automation Plan wizard using a threshold event filter selection.
Problem
A threshold that you create in the Event Automation Plan wizard can be modified, deleted, or deactivated using the Thresholds task that is available in System Status and Health. If you delete the threshold in the Thresholds task, then the event automation plan still contains the event type of the threshold but the values are no longer selected or are zeroed out.
Resolution
To correct the threshold event automation plan, you must edit the event automation plan and set the threshold values again. Then, save the event automation plan.
Unfamiliar event filters are displayed on the Event Filters page

This problem affects event automation plans that were created in the Event Automation Plan wizard.
Problem
The Event Filters page displays unfamiliar event filters.
119
Explanation
When you select a Common event type when using the Event Automation Plan wizard, an event filter is created that represents the selected event types. You cannot edit this event filter because the associated event automation plan is dependent upon it. Note: The filter name is plan_name-Filter, where plan_name is the event automation plan name.
Resolution
If the event automation plan is deleted, the event filter is deleted automatically.
Configuration manager troubleshooting

This section provides information about problems and workarounds for the configuration manager plug-in.
Configuration manager status is shown as Not Ready in the Welcome page

Configuration manager functions are not available.
Problem
The Manage tab of the IBM Systems Director Welcome page shows the status of Configuration Manager as Not ready. The configuration manager server, editor, or their dependent services might not be available. Also, attempts to use any of the configuration manager functions will result in the error message: ATKCOR031E An unknown error has occurred.
Investigation
Determine the status of the following: v Configuration Manager Server framework (com.ibm.director.configmanager) v Configuration Manager Editor framework (com.ibm.director.console.configmanager) v v v v v v v IBM BladeCenter and System x interface (com.ibm.director.bcxconfigmanager) Storage interface (com.ibm.director.storconfigmanager) CIM Client Factory service (com.ibm.usmi.client.cim.sblimimpl) Client service (com.ibm.usmi.client.services) Event Router service (com.ibm.usmi.kernel.USMIKernel Manageable Element service (com.ibm.usmi.kernel.USMIKernel) Persistence service (com.ibm.usmi.kernel.USMIKernel)
v Switch interface (com.ibm.sysmgt.vendor.switches) v Task service (com.ibm.usmi.kernel.USMIKernel) v Template service (com.ibm.usmi.services.template)
120
Explanation
Configuration manager functions are built on some of the core services available in IBM Systems Director Server. The configuration manager framework waits for all the dependent services be available before starting. The core services that Configuration Manager depends on are: v Chassis Information service v CIM Client Factory service v Client service v Event Router service v v v v Manageable Element service Persistence service Task service Template service
If any of these services are not available, the configuration manager functions are also not available. On AIX and Linux systems, use this command to list all the installed bundles with their status. This command directs the output to a file named output_file.txt. lwiplugin.sh -status > output_file.txt On Windows systems, use this command to list all the installed bundles with their status. This command directs the output to a file named output_file.txt. lwiplugin.bat -status > output_file.txt
Resolution
If the status of any of the services listed in the Investigation section is not ACTIVE, then try to manually start them. This command can be used to start a bundle manually: lwiplugin -start <bundle_name> This is an example command: lwiplugin -start <bundle_name> lwiplugin -start com.ibm.usmi.client.cim.sblimimpl This command is available in the lwi\bin directory under the IBM Systems Director home directory. If the manual start of the dependent bundles do not change the Configuration Manager availability status to Ready, and if the IBM Systems Director Server was installed using ISDServerSetup.exe (on the Windows platform), then contact your service provider. If the IBM Systems Director Server was not installed using ISDServerSetup.exe (on the Windows platform), then uninstall the IBM Systems Director Server and reinstall it using this install program.
121
Mass configuration fails to configure Asset ID information

This problem affects mass configuration and Asset ID configuration in the Configuration Manager task.
Problem
In the Configuration Manager task, when you use mass configuration and the Asset ID configuration template to configure Asset ID information, the configuration fails.
Explanation
The affected system does not have sufficient data space. When the size of the configuration is larger than that of the remaining data space, the configuration fails (although there is no indication that a failure has occurred). This is a limitation of the data save area. When in deferred mode, the template cannot determine the amount of data space on the system and uses 1024 bytes as a default amount. If the input exceeds 1024 bytes, the template prevents the configuration from being saved and the Deploy button is disabled. When the template is applied to a target system, the amount of actual data space is determined. If the amount of actual data space is insufficient, the information that exceeds the data space is lost and a message is logged in the following ways: v In the activation log. In the Configuration Templates table, select the template and then click Actions > Properties. In the Properties view, click the Logs tab. On the Logs page, select the job activation record. The activation log is displayed below the table. v In the install_root/log/configmgrplugin.log file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). When in immediate mode, the template determines the amount of data space on the target system. If the input exceeds the amount of available data space, the template prevents the configuration from being saved and the Deploy button is disabled.
Resolution
Make sure that the total bytes of data that you input does not exceed the maximum number of bytes that the data space can save on the managed resource.
Deploy of a configuration template fails on a target device that is not supported

This problem affects all areas that use configuration templates. A deploy task could hang and give no indication that anything is wrong with the task.
Problem
If you try to deploy a configuration template on a target device having a type that configuration template does not support, then you check progress of the deploy job, you will find that there is no progress bar displayed on the scheduled job properties page and its status is 'Active'.
122
Explanation
This can be caused by: v Attempting to deploy the configuration template on a target device where inventory collection has not been done or is outdated. v Attempting to deploy the configuration template on a target device whose device type is not supported by the configuration template. v Attempting to deploy the configuration template on a target device that is not accessible or broken.
Investigation
Examine the log files for device failures for the specific device that is the target of the deploy task.
Resolution
Before deploying a configuration template, make sure that: v Inventory collection is complete and current for the device. v The device is accessible and in working order. v The type of the target device on which you are deploying the configuration template is supported by the type of the configuration template.
Discovery manager (including inventory) troubleshooting

This section provides information for specific problems and workarounds associated with discovery and inventory in the IBM Systems Director environment.
Discovery troubleshooting
This section provides information for specific problems and workarounds associated with the Discovery task.
A Platform Agent managed system running VMware 3.5 is discovered as an agentless managed system
This limitation affects Platform Agent managed systems running VMware ESX 3.5 update 3.
Problem
After installing Platform Agent on a managed system running VMware ESX 3.5 update 3, the managed system appears in IBM Systems Director Web interface as an agentless managed system. This problem could occur in one of two circumstances: v The managed system is rebooted after installing Platform Agent but before adding and gaining access to the managed system in IBM Systems Director Web interface. v OpenPegasus is restarted on the managed system after installing Platform Agent but before adding and gaining access to the managed system in IBM Systems Director Web interface.
123
Explanation
This problem occurs because the version of OpenPegasus that is included with VMware ESX 3.5 update 3 has a built-in SLP service agent. When OpenPegasus starts, it takes control of port 427, removing the registration for the Platform Agent service agent.
Resolution
To resolve this problem after the managed system is rebooted or after OpenPegasus is restarted, issue the following command to start tier1slpinst again:
/etc/init.d/tier1slpinst restart
Note: This command is also used if you cannot request access to the managed system running VMware ESX 3.5 update 2 or update 3.
After a PPMO is deleted, it reappears in IBM Systems Director Web interface

This problem affects IBM Systems Director Web interface.
Problem
After a physical platform managed resource is deleted, it reappears in IBM Systems Director Web interface.
Investigation
Delete the managed resource or systems that are associated with the physical platform managed resource.
Allow time before discovery of a new switch

This problem affects users who discover, request access or remove switches using scripts.
Problem
When using a script to discover, request access, or remove switches automatically, a switch might be fully unlocked before request access has actually taken place.
Resolution
Before discovering a new switch, allow time before attempting another round of discovery.
Automatically requesting access to a previously discovered resource fails

This problem affects discoveries that use a discovery profile to automatically request access to one or more previously discovered resources.
Problem
When a discovery automatically requests access to a previously discovered resource to which IBM Systems Director currently does not have access, the access request fails. After the discovery process finishes running, the previously discovered resource to which IBM Systems Director did not have access still has a status of No Access. When the discovery process cannot access a resource, the
124
process also cannot collect inventory for that resource.
Explanation
Automatically requesting access applies only to resources discovered during the current discovery process. If a resource was discovered previously, the current discovery process retrieves existing information for that resource from the IBM Systems Director Server. Because the resource was discovered previously, the current discovery does not discover the resource, does not request access to the resource, and does not indicate an error.
Resolution
Remove the previously discovered resource to which you want to automatically request access. After removing the specified resource, running the discovery again successfully requests access to the resource.
Cannot add a management module or Remote Supervisor Adapter II to IBM Systems Director
This problem affects the IBM BladeCenter management module, advanced management module, and Remote Supervisor Adapter II.
Problem
When you add an IBM BladeCenter management module, advanced management module, or a Remote Supervisor Adapter II to IBM Systems Director, either of the following errors is displayed: Cannot Add BladeCenter Chassis or Cannot add device.
Resolution
To correct this problem, complete the following steps: 1. Using the Remote Supervisor Adapter Web application, log on to the affected management module or Remote Supervisor Adapter II. 2. In the left pane, click Network Protocols. 3. Make sure that TCP Mode Command Protocol is enabled. If it is disabled, enable it and restart the affected management module or Remote Supervisor Adapter II. 4. Repeat the process to add the affected management module or Remote Supervisor Adapter II to IBM Systems Director.
Cannot add a Windows 2003 system as an SNMP device

This problem affects SNMP-managed resources running Windows 2003.
Problem
Even if the SNMP service is installed and running, a Windows 2003 system cannot be added as an SNMP device to the IBM Systems Director environment.
Resolution
To resolve this problem, complete the following steps on the managed resource: 1. From the Windows 2003 desktop, click Start > Settings > Control Panel. 2. Double-click Administrative Tools.
125
3. 4. 5. 6. 7.
Double-click Services. Right-click SNMP Service and select Properties. In the SNMP Service Properties window, click the Security page. In Accepted Community Names group, click Add. Type the SNMP community assigned to you by your network administrator. Make sure you assign it with at least read rights. 8. Make sure that Accept SNMP packets from any host is selected. If you do not select this field, you must add the host name or IP address of your management server in the Accept SNMP Packets from these hosts area.
Cannot discover agent properly on managed system

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers. Problem: After you modify the IP address of a platform agent through the IBM Systems Director network configuration plug-in, rediscovering the platform agent through its new IP address interrupts CIM access. Explanation: This is a limitation for the platform agent, which will be solved in a future release. Resolution: Before you rediscover the platform agent through its new IP address, restart OpenSLP, tier1slp, and cimom on Linux; restart IBMSA, tier1slp, and wmicimserver on Windows.
Clones of Linux machines are not discovered or are merged

This problem affects Linux machines that were cloned.
Problem
When a Linux machine is cloned one or more times, some of the resulting machines are not discovered, or else they are merged.
Explanation
The secure shell (ssh) fingerprints are identical between the machines, so the discovery process does not recognize them as individual endpoints.
Resolution
1. In IBM Systems Director, delete any discovered targets for the cloned or copied systems. 2. Stop IBM Systems Director Server. 3. For each cloned machine, regenerate the keys for ssh by using the following commands:
ssh-keygen -q -f /etc/ssh/ssh_host_key -N -t rsa1 ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N -t rsa ssh-keygen -f /etc/ssh/ssh_host_dsa_key -N -t dsa
Do not provide a passphrase.
126
For more information about ssh-keygen, see the documentation for the Linux distribution running on the cloned machines. 4. Restart the ssh service for each machine. 5. Start IBM Systems Director Server. 6. Discover the cloned machines.
Common Agent managed systems are not displayed

This problem affects Common Agent.
Problem
Common Agent managed systems are not displayed in the IBM Systems Director Web interface.
Resolution
To correct this problem, make sure that the system is turned on, Common Agent is running, and the network connection is reliable.
Discovery does not create an SNMP managed resource for a IBM BladeCenter network device
This problem affects IBM BladeCenter network devices only.
Problem
The IBM BladeCenter chassis discovery process does not create an SNMP managed resource for a IBM BladeCenter network device.
Explanation
IBM Systems Director supports both public and non-public community names. If the community name of the SNMP managed resource of the switch module is not set to public, the IBM BladeCenter chassis discovery will not create an SNMP managed resource for that switch module. Also, the community name in the SNMP agent that is installed on the switch module must match the community name of the SNMP managed resource displayed in the IBM Systems Director Web interface for the SNMP managed object to stay online.
Resolution
Make sure that the SNMP community name in the SNMP agent of the switch module is set to public and matches the community name of the SNMP managed resource displayed in the IBM Systems Director Web interface. If you must use an SNMP community name other than public with a switch module, complete the following steps: 1. Set the community name in the SNMP agent that is installed on the switch module to public. 2. Run the IBM BladeCenter chassis discovery. IBM Systems Director creates an SNMP managed resource for the switch module and displays its status as Online. 3. Set the community name in the SNMP agent that is installed on the switch module to the new value. The IBM Systems Director Web interface displays the status of the switch module as Offline.
127
4. Change the community name in the SNMP managed resource to the new value. The status of the switch module is displayed as Online.
Discovery fails to discover a system on which Platform Agent was installed only moments before
This problem affects discoveries that use the Common Information Model (CIM) protocol to discover Windows Server 2008 R2 systems on which Platform Agent was installed only moments before.
Problem
When using the CIM protocol to discover resources, the discovery will fail when trying to discover Windows Server 2008 R2 systems on which Platform Agent was installed only moments before.
Explanation
After installing Platform Agent, Platform Agent services run an initialization process. On systems running Windows Server 2008 R2, the Platform Agent initialization process takes several minutes to complete. If a request to discover this kind of system is started before Platform Agent initialization finishes successfully, the discovery process fails to discover the system.
Resolution
After completing the installation of Platform Agent on a system that is running Windows Server 2008 R2, wait for approximately 8 minutes before trying to discover the system. Waiting 8 minutes gives Platform Agent services time to complete the initialization process, which enables discovery to successfully discover the system.
Discovery finds two operating systems for one discovered resource

This problem affects the discovery of a single resource that has multiple IP addresses where one or more of those IP addresses cannot be resolved correctly by the DNS server.
Problem
When discovering a single resource that has multiple IP addresses, the results in the resource table show two operating systems for the one resource. v The name of one operating system is the same as the resource host name. v The name of the other operating system is the unresolvable IP address.
Resolution
Use one of the following options to resolve this problem. If you cannot perform the first option, use the second option. 1. Enable the DNS server to resolve the currently unresolvable IP address. a. Add an entry for the unresolvable IP address to the DNS server. b. Remove the two operating systems from the resource table. c. Rediscover the resource. 2. Request access to both of the operating systems, which merges them into a single operating system.
128
Note: If the name of the merged operating system becomes the unresolvable IP address, simply rename it.
Discovery of Xen managed resources does not function correctly

This problem affects managed resources that are hosted by the virtualization service and occurs during the discovery process.
Problem
When you attempt to discover virtual resources that are hosted by a supported Red Hat Enterprise Linux or SUSE Linux system running the Xen Virtualization Management Service, the discovery attempt fails.
Explanation
Any of the following situations can cause this problem: v An unsupported version of Linux is installed on the agent system. v A firewall is blocking communication to the agent system. v Platform Agent is not installed on the agent system. v The Xen Virtualization Management Service is either not installed on the agent system or is not active on the agent system. v The CIM server is not active on the agent system. v The OpenSLP service is running on the agent system. v The IBM Systems Director SLP service is not running on the agent system. v The CMPXMI service is not running on the agent system. v The time difference between the agent system and the IBM Systems Director Server system is too large.
Resolution
To resolve this problem, complete the following steps to manage each of the potential source situations: 1. Ensure that you have a supported version of the Red Hat Enterprise Linux or SUSE Linux operating system installed on the agent system. For more information, see Operating systems supported by IBM Systems Director 6.1. 2. Ensure that there are no firewall problems from the IBM Systems Director Server system to the agent system and from the agent system to the IBM Systems Director Server system. For more information, see All available ports. 3. Ensure that Platform Agent is installed on the agent system. If it is not, install it. For more information, see Installing Platform Agent. 4. Ensure that the Xen Virtualization Management Service is active. First check if it is active by typing the following command and pressing Enter:
service xend status
If the Xen Virtualization Management Service is installed and active, the response will look similar to the following command output:
Checking status of xend (pid 4194 4195) running
If the Xen Virtualization Management Service is not active, then attempt to start it by typing the following command and pressing Enter:
service xend start
129
5. Ensure that Platform Agent is running by issuing the following set of commands that is appropriate for your operating system: System x /opt/ibm/icc/cimom/bin/cimcli ei CIM_ComputerSystem -n root/ibmsd --timeout 300 | grep Linux_ComputerSystem_instance System z /opt/ibm/icc/cimom/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grep Linux_ComputerSystem_instance Restart Platform Agent by stopping and then starting it: a. Stop Platform Agent by typing the following commands and then pressing Enter:
/etc/init.d/cimserverd stop /etc/init.d/tier1slpinst stop /etc/init.d/cimlistenerd stop /etc/init.d/ibmsa stop (Platform Agent 5.20.3x only)
b. Start Platform Agent by typing the following commands and then pressing Enter:
/etc/init.d/ibmsa start (Platform Agent 5.20.3x only) /etc/init.d/cimlistenerd start /etc/init.d/tier1slpinst start /etc/init.d/cimserverd start
6. Ensure that the CMPIXEN service is running on the agent system. Type the following command at the command prompt on the agent system and press Enter:
/etc/init.d/cmpixen status
If the CMPIXEN supplied SLP service is running on the agent system, the response will look similar to the following command output:
Checking for Xen CIM Services gathered running Checking for Xen CIM Services reposd running Checking for Xen CIM Services SLP registration running
If the CMPIXEN supplied SLP service is not running on the agent system, then start the CMPIXEN service by typing the following command and pressing Enter:
/etc/init.d/cmpixen start
7. For agent systems running the SUSE Linux operating system, ensure that the SLP service supplied by SUSE Linux is not running on the agent system. Type the following command at the command prompt on the agent system and press Enter:
/etc/init.d/slpd status
If the SLP service is not running on the agent system, the response will look similar to the following command output:
Checking for slpd unused
If the SLP service is running on the agent system, then use the YAST Control Center to disable the SLP service and ensure that the service is not started automatically at boot time. 8. Ensure that IBM Systems Director Server can communicate with the SLP service that is running on the agent system.
130
If IBM Systems Director Server is running on a supported Windows system, type the following commands at the system command prompt and press Enter after each command:
cd "C:\Program Files\Common Files\IBM\icc\slp\bin" slp_query.exe -type=service:management-software:virtual-system-management:XEN -address=ipaddr_of_agent
where ipaddr_of_agent is the IP address of the Platform Agent system. If IBM Systems Director Server is running on a supported Linux system, issue the following command:/opt/ibm/icc/slp/bin/slp_query --type=service:* --address=ipaddr_of_agent where ipaddr_of_agent is the IP address of the Platform Agent system. If IBM Systems Director Server can communicate with the SLP service on the agent system and the agent system is identified by the SLP service as a Xen system, the slp_query.exe command output will contain the following information:
URL: service:management-software:virtual-system-management:XEN
If IBM Systems Director Server cannot communicate with the SLP service on the agent system, then refer to the steps above and ensure that the following conditions are met: a. The IBM Systems Director SLP service is the only SLP service running on the agent system. b. Platform Agent is installed and running on the agent system. c. There are no firewall problems. d. The Xen Virtualization Management Service is installed and active on the agent system. 9. Ensure that the system date and time settings for the IBM Systems Director Server system and the agent system are as in synch as possible. If the system date and time settings for the IBM Systems Director Server system and the agent system are too far out of synch with each other, a potential result is that IBM Systems Director Server interprets this condition as a security certificate problem. So, ensure that the following conditions are met: v Ensure system v Ensure system that and that and the the the the system date setting for the IBM Systems Director Server agent system are set to the same calendar date. system time setting for the IBM Systems Director Server agent system are set within a few minutes of each other.
Discovery of resources with multiple NICs results in the discovery of extraneous managed resources
This problem affects resources with multiple network interface cards (NICs).
Problem
When using basic discovery methods in environments with agentless and multi-NIC systems, discovery produces multiple managed resources that represent the one resource.
Explanation
IBM Systems Director uses a number of techniques for uniquely identifying managed resources. It uses host names to identify operating systems but prefers to use IBM Systems Director's UniqueID value. The UniqueID value is far more reliable because it is defined for the operating system instance throughout the
131
system. A single-NIC system does not cause a problem because the same host name is returned no matter which discovery protocol is used. However, in a multi-NIC system with SSH and CIM, for example, you might discover and resolve the SSH access using one host name and the CIM using another host name. Because SSH provides no UniqueID value at discovery, the two are not correlated, and discovery interprets them as separate managed resources.
Resolution
When discovering resources that have multiple NICs and that have SSH, DCOM, or SNMP accessibility, perform the following steps: Note: The default profiles specified in the following steps discover only the IP addresses in your primary subnet and do not automatically request access to discovered resources. If you want to alter those behaviors, you must create a profile (perhaps based on a default profile). 1. Run the Default agentless discovery profile to discover any agentless-managed resources. 2. Request access to all newly discovered resources. 3. Run the following default profiles to discover any Platform Agent managed systems (CIM) or Common Agent managed systems (CAS\IPC): v Default Platform Agent and agentless discovery v Default Common Agent discovery 4. Request access to all newly discovered resources. To resolve this problem for a resource that is already discovered, request access to all the agentless-managed resources and Agent-managed resources that represent the one resource.
This solution works because, when an agentless system becomes accessible, a unique identifier (UID) is assigned to it. This UID is then used to properly correlate any additional Platform Agent or Common Agent functionality to the same resource.
Discovery results do not show CIM Remote Service Access Protocol

This problem affects some discoveries that use the Common Information Model (CIM) protocol.
Problem
After discovering a resource, you can view available Remote Service Access Protocols (RSAPs) for that resource in the discovery results (properties page or in other tables that list the resource). In some cases, the Common Information Model (CIM) protocol might be available but not shown. In Director 6.x, the Common Agent Services protocol, if present, handles the transport for CIM communication. This behavior works as designed, because tunneling CIM communication through Common Agent Services helps reduce the number of open, active ports that are required by IBM Systems Director.
132
Investigation
Determine that CIM communication is working properly by performing the following steps: 1. Run the following command on the resource:
cimcli -n root/ibmsd ns
2. If running the cimcli command correctly returns the namespaces, then CIM is working properly. Go to step 4. 3. If running the cli command does not correctly return the namespaces, then CIM is not working properly. Make sure that the Agent installed on the resource is properly configured. 4. From IBM Systems Director Server, run the command that is appropriate for your operating system and Platform Agent level: v On AIX or Windows:
slp_query --type=* --address=<ip_of_Agent-managed_resource>
v On Linux: Platform Agent 6.2.1 /opt/ibm/icc/bin/slptool -u ipaddr_of_agent findsrvs service:management-software.IBM:platform-agent where ipaddr_of_agent is the IP address of the Platform Agent system. Platform Agent 5.20.3x /opt/ibm/icc/slp/bin/slp_query --type=service:* --address=ipaddr_of_agent where ipaddr_of_agent is the IP address of the Platform Agent system. 5. If the SLP command results show two wbem entries (one http and one https), then the CIM service ports are discovered correctly and CIM communication works properly even if the RSAP is not shown. If the command results do not show both wbem entries, a different problem exists.
Explanation
The behavior described in this topic is a known limitation.
IBM BladeCenter discovery does not function correctly

This problem affects IBM BladeCenter products only.
Problem
A IBM BladeCenter discovery does not function correctly when multiple network interface cards (NICs) are enabled.
Resolution
To resolve this problem, complete the following steps. Note: You must do this each time you want to discover the IBM BladeCenter unit and its components. 1. Determine the NICs that are connected to the IBM BladeCenter unit network.
133
2. Disable all NICs except one, which must be able to communicate with the IBM BladeCenter management module. 3. Initiate discovery. 4. When the discovery is completed, re-enable the NICs that you disabled.
IBM Systems Director Server can lock upon RHEL5 and SLES10 Common Agent discovery
This problem affects users who attempt to discover a RHEL5 or SLES10 Common Agent.
Problem
Attempts to discover Red Hat Enterprise Linux, version 5.0 or SUSE Linux Enterprise Server 10 Common Agents might cause the IBM Systems Director Server to lock itself.
Explanation
This problem occurs if the xen-libs and xen-tools packages for RHEL5 or SLES10 have not been removed before installing the IBM Systems Director Server.
Resolution
Run the following commands to remove the packages from your system before installing IBM Systems Director Server:
32-bit rpm -e --nodeps xen-libs rpm -e --nodeps xen-tools 64-bit rpm -e --nodeps --allmatches xen-libs rpm -e --nodeps --allmatches xen-tools
Reboot after your run the commands.
Local system is not discovered at startup

This problem affects tasks that require that the local system is discovered at server startup.
Problem
The system on which IBM Systems Director Server resides is not discovered when the server is started. The following IBM Systems Director tasks are examples of those that will fail when the local system is not discovered: v Resource navigation of the local system v Update IBM Systems Director v Credentials
Explanation
The system on which IBM Systems Director Server is installed must be discovered and accessible or certain tasks will fail.
134
Resolution
The following are some potential reasons why the system was not discovered and possible resolutions for each: IBM Systems Director Server has just started and the agent might not be fully started yet. Wait 15 minutes and try again. A firewall installed on the system on which IBM Systems Director Server is installed is preventing communication between the server and agent. Ensure that the appropriate ports are set to allow access through the firewall. For information about which ports to set, see All available ports.
Non-IBM hardware shown as offline after discovery

This problem affects non-IBM hardware. After discovery, the Server resource (not the Operating System resource) that represents the hardware has an access state of Offline.
Problem
Note: IBM Systems Director 6.1 Common Agent is supported on non-IBM systems. Platform Agent is not supported on non-IBM systems. After discovering and requesting access to non-IBM systems, the Server resource (not the Operating System resource) that represents the system has an access state of Offline. The access state might first be labeled Unknown, but after using the Verify connection task, the state access changed to Offline.
Resolution
To resolve this problem, make sure that the baseboard management controller (BMC) in the non-IBM system is correctly configured for out-of-band communication. See the system documentation for information about configuring the BMC.
SSH protocol not discovered for AIX IPv6 agents

This problem affects systems running AIX.
Problem
The SSH protocol is not discovered for AIX agents running in an IPv6 environment.
Investigation
The problem is due to the IPv6 related entry missing in the sshd configuration file. To confirm the problem, try to SSH to the system:
ssh <ipv6 address>
If the result is the following message, review the configuration steps to resolve this problem.
ssh: connect to host <ipv6 address> port 22: Connection refused
Resolution
1. Edit /etc/ssh/sshd_config so that the configuration for Port 22 is as follows:
135
#Port 22 AddressFamily any ListenAddress 0.0.0.0 ListenAddress ::
2. Stop sshd services stopsrc -s sshd 3. Restart sshd services startsrc -s sshd
System discovery results in assignment of the IP addresses to existing systems

This problem affects primarily networks where DHCP is used, but might occur whenever there is not a consistent mapping from a DNS host name to a physical system.
Problem
When you perform a discovery action to find new systems, the systems are not displayed in the resources views. Instead, the IP addresses seem to be assigned to existing systems.
Explanation
The IBM Systems Director Server uses the host names of the managed systems to match systems that are discovered using multiple protocols or at different times. Having a consistent mapping of host names to systems ensures that other systems are not matched to previously discovered systems. Example: Consider a system at address 192.168.1.5 in a DHCP environment without dynamic DNS. Suppose the host name that resolves to that address is s5.example.com. Later, the address of the system changes to 192.168.1.9, which maps to host name s9.example.com. If the system is rediscovered at that address, IBM Systems Director will consider it as a new system because it has a different host name, and a new manageable system is created. Likewise, if another system acquires the host name s5.example.com and is discovered, IBM Systems Director will consider it as the same system as originally discovered at s5.example.com. Discovering only Common Agents causes the system matching process to use the unique identifier of the systems, and the host name is not used.
Resolution
IBM Systems Director requires that a host name is consistently resolved to the same system, even if the IP address of the system changes. Try the following solutions to accomplish this resolution: v Use static IP addresses. v Have a working dynamic DNS with DHCP, so that a system has a consistent host name. v Ensure that DHCP always assigns the same address to a system. v Use a hosts file on the server to ensure consistent mapping of host names to systems. v Install only Common Agents and use a discovery profile to find only those agents.
Unable to discover some I/O modules using SNMP

This problem affects switch and bridge modules only.
136
Problem
When you attempt to discover a switch or bridge module using SNMP, the discovery fails.
Explanation
This problem affects switch and bridge modules that do not correctly provide the MAC address for the management connection in SNMP. The MAC address is required for IBM Systems Director to uniquely identify the module that has been discovered.
Resolution
There are two possible resolutions: v If available, download a new version of the I/O module firmware that fixes the problem. v If the affected I/O module is a BladeCenter component, discover the BladeCenter chassis and then request and receive access to that chassis. Doing so will discover the I/O module. Note: If the chassis was discovered before the I/O module was inserted, you can discover the I/O module in the following ways: Select the affected chassis and click Actions > Security > Verify Connection. On the Verify Connection page, select Query vital properties and click Verify Connection. Select the affected chassis and click Actions > Inventory > View and Collect Inventory and perform an inventory collection.
Inventory troubleshooting
This section provides information for specific problems and workarounds associated with the Inventory task.
Inventory collection completes with errors

This problem affects collecting inventory for System x systems that are running Linux.
Problem
Collecting inventory for a System x system that is running Linux completes with errors.
Explanation
To retrieve vital product data (VPD) information from the system BIOS of a System x system that is running Linux, IBM Systems Director must have root access. If the inventory collection does not have root access, it cannot read the physical memory to get this information. In this situation, collecting inventory without root access causes inventory collection to complete with errors. Requesting access to the system as a user that is in the root group does not satisfy this access. IBM Systems Director must either run as the root user explicitly or use the sudo utility.
137
Resolution
When requesting access to and collecting information for a System x system that is running Linux, perform one of the following actions: v Use the root user to access and collect inventory. v For systems running Common Agent, install and start the service for the agent as root. v For IBM Systems Director 6.1.2 and later, when accessing and collecting inventory for agentless-managed systems, you can use the sudo utility to configure those systems to allow IBM Systems Director to run as a user other than root. For more information about using the sudo utility to configure agentless-managed systems to use a user other than root, see Configuring access to agentless managed systems..
Inventory collection fails

Problem
Inventory collection fails if IBM Systems Director Server is an older version than Common Agent or Platform Agent.
Resolution
IBM Systems Director Server must be the same version or a later version than Common Agent or Platform Agent. Update your IBM Systems Director Server installation.
Inventory collection fails to complete for IBM BladeCenter chassis

This problem affects only IBM BladeCenter chassis products.
Problem
You have discovered a IBM BladeCenter chassis successfully, but, when you run inventory collection on the IBM BladeCenter chassis, the collection is not completed.
Resolution
Before running inventory collection on a IBM BladeCenter chassis, you must enable SNMP using the Management Module Network Configuration component of configuration manager. See Configuring an IBM BladeCenter management module in the IBM Systems Director Systems Management Guide for more information.
Collecting inventory fails to retrieve software details from blade chassis

This problem affects inventory collection for a blade chassis and firmware upgrades for the chassis.
138
Problem
Collecting inventory for a blade center chassis does not return information about the software of the blade chassis, even when the task of collecting inventory completes successfully. The missing software information about the blade chassis includes details about the installed firmware version and any applied updates. Having incomplete software information prevents you from upgrading the firmware that is installed on the blade chassis.
Resolution
To resolve this problem, you need modify certain settings for the associated Advanced Management Module (AMM). Make the following changes by using the management-module Web interface. For more information, see AMM Web interface. After you open and log in to the management-module Web interface, configure the following MM Control network protocol settings: v Enable the SNMPv1 network protocol, and set the trap IP destination to 0.0.0.0. v Enable the SNMPv3 network protocol, then configure the SNMPv3 settings for the associated login profile: Set the authentication protocol to None Set the privacy protocol to None Leave the password fields blank Set the access type to Set Set the IP address for traps to 0.0.0.0 After you modify the AMM settings as previously indicated, collecting inventory again for the blade chassis retrieves the missing software information.
Root directory needs more space for AIX and Linux inventory collection
This problem affects inventory collection for AIX and Linux systems.
Problem
If you try to collect inventory for an AIX or Linux system, the process might fail if the root directory for the system does not have the required storage (1-2 MB).
Resolution
In the system with the installed Common Agent, you need to allocate extra disk space to the root directory (/) and delete the directory /tivoli/cce, if it already exists. You must then restart IBM Systems Director. If there is an IBM Systems Director Server installed on the system, you must restart it, as well.
Security and requesting access troubleshooting

This section provides information for specific problems and workarounds associated with security and accessing resources in the IBM Systems Director environment.
Access request to IBM Director Agent 5.20 fails

This problem affects IBM Director Agent 5.20 on systems running AIX .
139
Problem
When IBM Systems Director Server 6.1 requests access to an AIX system running IBM Director Agent 5.20, the request access fails immediately even though the user name and password are correct.
Explanation
The user name used for the request access is not authorized. In the NativeUserGroupsAIX.prop file, the line priv.groups.SecMgr defines the groups that can request access or login to IBM Director Agent.
Resolution
To resolve this problem, complete one of the following procedures: Updating the group file on the IBM Director Agent-managed system 1. In the /opt/ibm/director/data directory, open the NativeUserGroupsAIX.prop file and view the predefined IBM Systems Director security groups. 2. In the /etc directory, edit the group file to add the user name to one of the predefined groups and save the changes. For example, to add the root user to the dirsuper group, you must add the following entry:
dirsuper:!:group:root
where group is the group ID for the dirsuper group. Updating the NativeUserGroupsAIX.prop file on the IBM Director Agent-managed system 1. In the /etc directory, view the group file to determine the group to which your user name belongs. For example, the following line indicates that the root user belongs to system group:
system:!:0:root,esaadmin
2. In the /opt/ibm/director/data directory, edit the NativeUserGroupsAIX.prop file. 3. Add the affected group to the priv.groups.SecMgr line. For example, to add the system group, add the following entry:
priv.groups.SecMgr=security,root,diradmin,dirsuper,system
4. Stop IBM Director Agent by typing the following command on the managed system:
install_root/bin/twgstop
where install_root is the root directory of the IBM Director Agent installation. 5. Start IBM Director Agent by typing the following command on the managed system:
install_root/bin/twgstart
where install_root is the root directory of the IBM Director Agent installation.
140
SNMP remote service access point of a switch goes offline after switch creation and stays offline after request access
This problem affects users who are trying to create a switch through request access to a BladeCenter.
Problem
This problem occurs when a switch is created after requesting access to a BladeCenter. The IBM Systems Director Web interface shows the SNMP service access status of the switch as Offline and no access; the switch access status might be partially unlocked or locked. If you request access to the switch by using the request access task and typing a user ID and password, the access status might still show that the SNMP remote service access point of the switch is offline with no access.
Investigation
To check the status of the switch, in the IBM Systems Director Web interface, right-click the switch managed resource and then click Security > Configure Access.
Explanation
When the switch is created, IBM Systems Director tries to use the default community name public or the community names in <director install>\data\snmp\snmpdevice\snmpCommunities.properties and the SNMPv1 protocol to verify the SNMP connection. If the community name is not the default or is not listed in the properties file, the verify connection task fails, which causes the SNMP remote service access point of the switch to be locked. Then, if you request access to the switch on the Request Access page, you can provide only a user ID and password. Because no SNMP credential is provided, the SNMP remote service access point of the switch stays locked. It can be unlocked when an SNMP credential is created.
Resolution
To resolve this problem, create an SNMP credential by completing these steps: v Click the SNMP switch and then click Configure Credential. v In the Configure Credential wizard, if the Welcome page is displayed, click Next. v For the credential type, select SNMP v1/v2c and then click Next. v Specify the switch community name in the credential details. v Click Next and then click Finish.
Request Access password length restriction

Problem
When requesting access to a secured system from the Request Access page, you cannot enter a password longer than 45 characters.
141
Explanation
The Request Access task has a password length limit of 45 characters. Additional characters will be ignored. You cannot gain access to a managed system using a user credential that has a password greater than 45 characters in length.
Resolution
To correct this problem, shorten the password on the managed system to gain access.
Access request to a managed system running SUSE Linux Enterprise Server fails
This problem affects access requests to managed systems that are installed with Common Agent or Platform Agent and are running SUSE Linux Enterprise Server.
Problem
When you request access to a Common Agent managed system or Platform Agent managed system that is running SUSE Linux Enterprise Server, the access request fails and the affected system is not displayed as type Server in the IBM Systems Director IBM Systems Director Web interface. That is, the agent is discovered, but access to the system is not obtained.
Investigation
Check the /etc/host file on the affected system to determine if an entry for the IP address 127.0.0.2 exists. In the file, determine if a line similar to the following line is present:
127.0.0.2 server.company.com server
where v server.company.com is the fully qualified host name. v server is the short host name.
Explanation
This problem results from the existence of an entry in the /etc/hosts file for the IP address 127.0.0.2. This entry results in IBM Systems Director identifying the IP address of the affected system as 127.0.0.2. Some IBM Systems Director functions on the affected managed system and the management server will fail to work as designed when this situation occurs. Important: Using the DNS and host name configuration function of the YAST system tool inserts a 127.0.0.2 entry into the /etc/hosts file.
Resolution
To resolve this problem, complete the following steps: 1. In the /etc/hosts file on the affected managed system, comment out the 127.0.0.2 entry. Insert the pound sign symbol (#) in the first character position of the entry, for example:
# 127.0.0.2 server.company.com server
where
142
2. 3. 4. 5.
v server.company.com is the fully qualified host name. v server is the short host name. Save the /etc/hosts file. Restart the affected managed system. In the IBM Systems Director IBM Systems Director Web interface, delete the affected system. Run System Discovery to discovery the affected system.
Agentless or Platform-Agent managed resource cannot be accessed

This problem only affects Agentless or Platform-Agent managed resources running IBM i.
Problem
An Agentless or Platform-Agent managed resource that is running IBM i cannot be accessed.
Resolution
To resolve this problem, make sure that Open SSH, *BASE and Option 1, Licensed Product Offering 5733-SC1 is installed and configured. Also make sure that SSH is running on the affected Agentless or Platform-Agent managed resource.
Managed resource state is Unknown

Problem
After you change encryption settings, certain managed resources cannot be managed and their state is listed as Unknown.
Explanation
This problem might be caused by one of the following circumstances: v When you request a new key or a cipher algorithm, IBM Systems Director must perform a presence check. This presence check might not be completed immediately. During the delay, IBM Systems Director Server cannot manage the system. v If you disable encryption on the management server, encrypted managed systems can no longer be managed. However, these systems might seem to be manageable for a certain period before they are displayed as locked.
Resolution
To correct this problem, force an immediate exchange of keys on a particular managed resource by requesting a presence check.
Credential mapping wizard does not finish when editing a credential mapping
This problem affects credential configuration.
143
Problem
When editing a credential mapping, clicking Finish on the summary page of the credential mapping wizard does nothing and no message is displayed to indicate that there is a problem.
Explanation
The credential mapping wizard cannot complete successfully if one or more of the following situations occurs after you have launched the wizard to edit a credential mapping: v The credential is deleted v The credential mapping is deleted
Resolution
Close the credential mapping wizard.
Settings permission is not available to users in groups other than smadmin

Problem
When you assign a role with only the Settings permission to a user that is in a group other than smadmin, the user does not receive authorization to modify settings as expected. When that user signs in to the IBM Systems Director Web interface, the Settings option is not displayed.
Resolution
To have the authorization to see the Settings option in the IBM Systems Director Web interface and modify the settings, the user must belong to the smadmin group.
Hardware Management Console access state becomes unknown after supplying incorrect credentials
This problem affects Hardware Management Consoles.
Problem
When you request access to a Hardware Management Console using incorrect credentials, the access request fails and the Hardware Management Console's access state changes to Unknown. Also, you are not able to request access again and verification of the connection will fail.
Explanation
Incorrect credentials prevent access to a Hardware Management Console. You cannot access request again because the Hardware Management Console is not in a state of No Access.
144
Resolution
Remove the Hardware Management Console and then rediscover the same Hardware Management Console.
Trust domain users cannot log on

This problem affects trust domain users that cannot log on to the IBM Systems Director Web interface on Windows.
Problem
In a trust domain environment with domain A and domain B, IBM Systems Director Server is installed on system C, which belongs to domain A. Users of domain A and domain B belong to the IBM Systems Director Server smadmin group on system C. Only the domain user (the domain A user) has the correct authority to log on to the IBM Systems Director Web interface while the trust domain user (the domain B user) has no authority to log on to the IBM Systems Director Web interface.
Resolution
Complete the following steps to provide the trust domain user (the domain B user) with the proper authority needed to log on to the IBM Systems Director Web interface: 1. Add a new domain A user (user D) in the smadmin group on system C. 2. Open Start menu > Settings > Control Panel > Administrative Tools > Services. 3. Right-click the IBM Director server service and select Properties. 4. 5. 6. 7. On the Log On page, select This account: and click Browse. Select the new user (user D) from domain A and click OK. Enter and reenter the correct password for user D and click OK. Right-click the IBM Director server service and select Restart.
Spaces are not allowed for LDAP user full DN

This problem affects users who employ LDAP user to login to the IBM Systems Director Web interface.
Problem
If you add an LDAP user to the LDAP group and it has spaces at the end of the full DN, the user will login as unknown.
Resolution
Remove spaces at the end of the LDAP user and re-login. The user will then have correct authority in the IBM Systems Director Web interface.
LDAP users unable to login when users in same path exceed 500
This problem affects IBM Systems Director Servers running on all systems when configured to use tivoli Directory server as authentication registry.
145
Problem
IBM Systems Director Servers are unable to allow users to log on to an LDAP server if the number of users under one path is more than 500.
Explanation
You can check the value of ibm-slapdSizeLimit by editing the ids_directory\etc\ibmslapd.conf file located on the IBM Systems Director Server.
Resolution
The default value of ibm-slapdSizeLimit is 500. To resolve this problem, increase the ibm-slapdSizeLimit parameter to a higher value.
DN values for securityldap.properties must match the LDAP server base values
This problem affects IBM Systems Director Servers running on AIX systems.
Problem
IBM Systems Director Servers running on AIX systems are unable to allow users to log on to an LDAP server if the LDAP server's /opt/ibm/director/lwi/conf/ overrides/securityLDAP.properties file specifies the base distinguished name (DN) value with the incorrect case.
Investigation
You can check the case of the DN value by editing the /opt/ibm/director/lwi/ conf/overrides/securityLDAP.properties file to confirm that the DN values have the correct specification. For example, if the LDAP server base uses uppercase for its DN values, such as dc=DOMAIN,dc=COM, but the values specified in the securityLDAP.properties file are in lowercase, such as dc=domain,dc=com, this will cause an error.
Resolution
For IBM Systems Director Servers running on AIX systems, set the com.ibm.lwi.security.username.caseSensitive flag to false and make sure that the base DN values specified in the securityLDAP.properties file match the LDAP server base values.
IBM BladeCenter and System x management troubleshooting

This section provides information about problems and workarounds for the IBM BladeCenter and System x management plug-in. This information includes the IBM BladeCenter and System x specific templates provided for the configuration manager plug-in.
Access is not granted automatically to switches

This problem affected switches that use a default user ID and password.
146
Problem
Some switches use a default user ID and password. After the switches are created, IBM Systems Director Server does not automatically grant access to the switches.
Resolution
To request access, enter the user ID and password from the command line or in the IBM Systems Director Web interface.
IBM Systems Director cannot communicate with out-of-band systems

This problem affects systems that IBM Systems Director manages through out-of-band communication. An affected system must include a management module, advanced management module, Remote Supervisor Adapter, or Remote Supervisor Adapter II.
Problem
IBM Systems Director fails to communicate with a system that is managed through out-of-band communication. Examples of failed communication can include: v Access requests fail v Inventory collection fails v Configuration manager fails to deploy plans or templates
Investigation
This problem can affect systems that use one of the following components: v Management module v Advanced management module v Remote Supervisor Adapter v Remote Supervisor Adapter II Note: If your system uses an Intelligent Platform Management Interface (IPMI) baseboard management controller (BMC), this problem does not affect the system.
Explanation
IBM Systems Director Server uses the standard TCP Command Mode protocol to communicate with these service processors and management modules. Other IBM programs use the standard TCP Command Mode protocol to communicate with service processors and management modules also, for example: v IBM Management Process Command-Line Interface (MPCLI) v UpdateXpress v Cluster Systems Management v Active Energy Manager (Standalone edition) By default, service processors and management modules are enabled to use the standard TCP Command Mode protocol and permit only one connection at a time when using the standard TCP Command Mode protocol. In this situation, if a system is communicating with another IBM program that uses the standard TCP Command Mode protocol, IBM Systems Director Server cannot communicate with that system. However, you can use the management module or Remote Supervisor Adapter (RSA) interface to increase the number of connections allowed.
147
Resolution
Close the program that is using the standard TCP Command Mode protocol to communicate with the service processor or management module. Important: Do not disable the standard TCP Command Mode protocol. IBM Systems Director Server can use connection. If the affected system uses an advanced management module, you can increase the number of connections permitted when using the standard TCP Command Mode protocol. Log into the advanced management module Web interface and view the Network Protocols page. On this page, the TCP Command Mode section provides a setting that you can change to increase the number of connections. This setting is available only for advanced management modules. The default setting for the number of connections permitted can vary depending on the firmware version installed. Check the TCP Command Mode section to determine the current default setting.
The server reports that "Power off and Restart" was successful, but it was not
Running "Power Off and Restart" against a server managed endpoint reports that it was successful, but the restart did not happen.
Problem
Instead of turning off the server and restarting, the operating system is prompting the user to decide whether to let the server restart. This error is seen on servers with the RH5.x Linux operating system installed.
Investigation
Determine whether the operating system is showing a prompt that requires user input.
Explanation
The Integrated Management Processor (iMM) signals the operating system to shut down and then assumes that the operating was shut down. However, if the operating system is configured to prompt the user, then it does so and waits for the user's input. This setting lets a user ensure that the server is not turned off or restarted by accident.
Resolution
If this behavior is configured on the operating system but is not desired, change the operating system configuration. For example, to change the configuration, on the RHEL 5.4 operating system, follow these steps: 1. Go to System > Preferences > More Preferences > Power Management > General. 2. For When power button is pressed, select Shutdown.
148
Full access to a QLogic or Nortel switch is not permitted with user ID and password
This problem affects QLogic and Nortel switches.
Problem
When you request access to a QLogic or Nortel switch with a user ID other than the original equipment manufacturer (OEM) user IDs, only partial access is granted. Note: This problem does not affect the following OEM user IDs: v QLogic: USERID v Nortel: admin
Resolution
To resolve this problem, complete the following steps: 1. Determine whether you can access the switch using Telnet. Select the affected switch resource and click Actions > Security > Configure Access. 2. Make sure the required switch vendor plug-in installed. For detailed information, see Downloading and activating BladeCenter I/O module plug-ins. 3. Use the applicable OEM user ID to request access: v QLogic: USERID v Nortel: admin
The Hardware Log task is not available

This problem affects System x systems.
Problem
When you right-click a System x system, the pop-up menu does not provide Hardware Log as a selection. Also, if you select a System x system and click Actions, the Hardware Log task is not available as a selection.
Investigation
In the table, view the affected resource row: v In the Type column, determine if the resource is of type Operating System or Server. v In the Access column, determine if you have Full access to the resource.
Explanation
To access hardware logs, you must work with a resource of type Server. This resource type represents the service processor. You must have full access to the resource. You also can work with Common Agent or Platform Agent. For Common Agent and Platform Agent, in order to use the Hardware Log task the following criteria must be met:
149
v The agent must be installed on an IBM server with a service processor that support the Hardware Log task. v You must have full access to the Operating System resource that represents the server. v You must have full access to the Server resource that represents the server. The following service processors support the Hardware Log task: v Intelligent Platform Management Interface (IPMI) baseboard management controller (BMC) v Remote Supervisor Adapter II v Remote Supervisor Adapter v IBM BladeCenter management module v IBM BladeCenter advanced management module
Resolution
To resolve the problem, complete the applicable step: v If the resource is of type Server but you do not have access, request access to the resource. v If the resource is of type Operating System, select the resource and click Actions > Related Resources. If a related resource is of type Server, select and use that resource to access the hardware logs. If there is no related resource of type Server, discover and request access to the service processor of the affected system. After you have full access to the Server resource, the Hardware Log task is available on the pop-up menu for both the Server and Operating Systems resources.
Incorrect events reported for NICs that have a teaming configuration of active-standby
The problem affects the reporting of events for managed resources where teaming (or bonding) for any active network interface card (NIC) is configured as active-standby. The problem is limited to NICs installed in managed systems that are running any supported Windows operating system.
Problem
When a network interface card (NIC) in a managed system has a teaming configuration of active-standby, IBM Systems Director incorrectly reports some events for that NIC. Note: Usually, an NIC is configured as active-standby only when the managed resource contains more than one active NIC.
Explanation
Currently NIC teaming supports only an active-active configuration. Because NIC teaming does not support an active-standby configuration, associated events are limited to SwitchOver and SwitchBack. Look for NIC teaming events in the Systems Director Event Log for the managed server (out-of-band) and in the Service Processor Console web user interface.
150
Table 4. Expected and reported events for NIC with teaming set to active-standby NIC teaming Primary = Failed Secondary = Active Symptom Primary NIC fails; teaming switches from primary NIC to secondary NIC Expected event* SwitchOver Reported event SwitchOver
Primary = Active Primary NIC comes Secondary = Standby online, teaming switches from secondary NIC to primary NIC Primary = Active Secondary = Failed Standby NIC fails
SwitchBack
SwitchBack
Offline Online
SwitchOver SwitchBack
Primary = Active Standby NIC comes Secondary = Standby online
* A network interface card with a teaming configuration of active-active correctly reports the expected NIC events.
Resolution
The problem identified in this topic is a known limitation for NICs with a teaming configuration of active-standby.
LED Status column is unavailable in Navigate Resources

This problem affects resources that do not support light path diagnostics.
Problem
When viewing a group of resources in Navigate Resources, you attempt to customize the displayed columns in the table by adding the LED Status column. However, the LED Status column is not available for selection.
Explanation
The LED Status column is available only when all the resources in the Navigate Resources view support light path diagnostics. In IBM Systems Director 6.1, the Operating System and Computer System resource types support light path diagnostics. Also, the default groups called All Operating Systems and All Systems can display the LED Status column.
Resolution
View a group that includes only the resource types that support light path diagnostics. Then, click Actions > Columns and add LED Status to the Selected columns list.
LED Status column does not report hardware problems

This problem affects systems that support light path diagnostics: System x systems and BladeCenter chassis.
151
Problem
A system has one or more light path diagnostic LEDs turned on. However, when you view the system in Navigate Resources, the LED Status column always reports the status as OK. Also, no light path diagnostic LED events are generated.
Explanation
Currently, IBM Systems Director provides LED Status support for System x systems and BladeCenter chassis. System x systems must have Common Agent or Platform Agent installed. Otherwise, the LED Status will not function and the reported status will default to OK. It is also possible that the affected system requires an updated Intelligent Platform Management Interface (IPMI) driver installed on it.
Resolution
Install Common Agent or Platform Agent on the affected System x system. If the light path diagnostics LED Status column still reports OK, update the IPMI driver on the system.
Out-of-band events are not configured correctly

This problem affects events that are sent to IBM Systems Director through out-of-band communication.
Problem
The Service Processor > Configuration event with a condition value of Failed is logged in the IBM Systems Director event log. This event is generated by IBM Systems Director Server when it determines that out-of-band events are not configured correctly.
Investigation
This problem can affect systems that use one of the following service processors or management modules: v Management module v Advanced management module v Remote Supervisor Adapter v Remote Supervisor Adapter II v Intelligent Platform Management Interface (IPMI) baseboard management controller (BMC)
Explanation
When you gain access to the system, the affected service processor or management module is configured automatically to send out-of-band events to IBM Systems Director Server. However, if a service processor or management module has exceeded its maximum number of alert recipients, the automatic configuration will fail and the Service Processor > Configuration event with a condition value of Failed is generated.
152
Table 5. Maximum number of alert recipients Service processor or management module Management module Advanced management module Remote Supervisor Adapter Remote Supervisor Adapter II IPMI BMC Maximum number of alert recipients 12
Typically 4, but might vary by system
Resolution
To resolve this problem, reduce the number of alert recipients for the affected service processor or management module and then add IBM Systems Director Server as an alert recipient. You can check the number of alert recipients using the configuration manager task called Current Configuration. To reduce the number of alert recipients, configure the alert-recipient settings using the applicable configuration manager template: Service Processor Alert Recipients or Management Module Alert Recipients. The Service Processor > Configuration event does not have a complementary resolution event. Therefore, you must manually clear the event from status after you have resolved the problem. Note: IBM Systems Director will not attempt to automatically configure out-of-band events again, unless access to the affected system access revoked and then access is granted access.
Out-of-band tasks fail on IPMI managed systems

This problem affects only System x and xSeries servers with IPMI baseboard management controllers.
Problem
IBM Systems Director tasks that interact out-of-band with servers that have Intelligent Platform Management Interface (IPMI) baseboard management controllers (BMC) might fail intermittently. Such tasks include Power Management, System Identification, Configuration Manager, and Management Processor Command-Line Interface (MPCLI).
Investigation
Out-of-band IPMI commands use the Remote Mail Checking Protocol (RMCP). In some network environments, the response packets might be delayed, causing intermittent failure of these commands. Increasing the IPMI-timeout setting can improve the receipt of the response packets.
Resolution
To resolve this problem, complete the following steps on the management server: 1. With an ASCII text editor, open the install_root\data\ asmDefinitions.properties file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
153
2. Increase the ipmi.timeout value. The default is 5000, which is equal to 5 seconds. 3. Save and close the file. 4. Stop IBM Systems Director Server by going to the command line, typing the applicable command, and pressing Enter.
For Linux For Windows install_root/smstop net stop DirServer
where install_root is the root directory of your IBM Systems Director installation. 5. Start IBM Systems Director Server by going to the command line, typing the applicable command, and pressing Enter.
For Linux For Windows install_root/smstart net start DirServer
where install_root is the root directory of your IBM Systems Director installation.
Power tasks vary by the resource

This problem affects systems that are supported by the Power On/Off task.
Problem
Depending on the resource, the available Power On/Off tasks vary.
Explanation
Support for the Power On/Off task varies depending on the following criteria: v The operating system that is running on the resource. v Whether Wake on LAN is installed on the resource v Whether out-of-band communication is configured for the resource Note: To access power state management tasks for blade servers in an IBM BladeCenter, you must first discover and request access to the management module.
Predictive Failure Analysis events not reported for System x3755 M3 servers
The problem affects the reporting of Predictive Failure Analysis events from managed IBM System x3755 M3 servers.
Problem
Platform Agent fails to report Predictive Failure Analysis events for processors or DIMMs that occur on x3755 M3 servers. Because the specified events are not reported, you cannot see any of those events in the event log for the operating system of the managed server.
154
Explanation
Because x3755 M3 servers use a non-IBM baseboard management controller (BMC), the following situations occur: v The BMC firmware on a x3755 M3 server does not detect the Predictive Failure Analysis sensors for processors and DIMMs v IBM IPMI firmware commands do not work on x3755 M3 servers Platform Agent cannot report the specified events unless detection of and support for Predictive Failure Analysis sensors and support for Predictive Failure Analysis sensor events is added to the non-IBM BMCs.
Resolution
The failure to report Predictive Failure Analysis events is a known limitation that is specific only to System x3755 M3 servers. You can view Predictive Failure Analysis events in the IBM Systems Director event log for the managed x3755 server (out-of-band). Additionally, you can use the service processor console web interface to view the events.
Switch access state remains Partial Access after access request

This problem affects IBM BladeCenter switches.
Problem
After a switch managed resource is created, the access state of the switch is typically Partial Access. Request access to switch with the correct user ID and password, the access states of some switches are still partial access. But firmware update can be successful after request access.
Investigation
Check the access state of the Telnet and HTTP access point using either of the following ways: v From the command line, type smcli lssystemdb switchGUID where switchGUID is the GUID associated with the switch. v In the IBM Systems Director Web interface, right-click the switch managed resource and then click Security > Configure Access.
Explanation
A switch can have some or all of the following access points related to it: v Switch SNMP v Switch Telnet v Switch HTTP v IBM BladeCenter TCM v Storage Provider SMIS (if it is managed through a storage provider) v PCL (for SAS) The switch access state is a combination of all the states of related access points. When all of the access points are in the Full Access state, the switch managed resource state is OK. If none of the access points are in the Full Access state, the switch access state is No Access. Otherwise, the switch access state is Partial Access.
155
When the switch managed resource is created, IBM Systems Director Server attempts to unlock the SNMP access point using the public, or user predefined, community name. The chassis access point is unlocked if the switch is created through the chassis. Therefore, the switch is initially in the Partial Access state. The update manager and configuration manager plug-in use only the Telnet and HTTP access types. When the switch managed resource is created, these two access points are in the No Access state. After you request access using the user ID and password, IBM Systems Director Server attempts to verify the credentials against switch. When all the access types are not in the Full Access state, the switch state remains Partial Access, but the individual RSAP state might be different.
Resolution
If you provide the correct user ID and password, but Telnet is not in the Full Access state, check to see if a switch vendor plug-in is required. For detailed information, see Downloading and activating BladeCenter I/O module plug-ins.
The System Identification menu options are not available

This problem affects resources of type Server.
Problem
When working with a resource, the System Identification task is not available on the pop-up menu and the Actions menu or the System Identification task does not provide options on the pop-up menu or the Actions menu.
Explanation
This problem can be caused by either of the following situations: v The System Identification task is only available for systems to which you have access. v The System Identification task is only supported for systems in which the service processor is configured correctly. The following service processors are affected: Remote Supervisor Adapter Remote Supervisor Adapter II Management module Advanced management module Baseboard management controller
Resolution
To resolve this problem, complete the applicable procedure For a resource to which you do not have access Complete the following steps: 1. Select the resource and click Actions > Security > Request Access. 2. Type the applicable user name and password. When the access state changes to Full, the System Identification task is available on the menu.
156
For an unresponsive processor For the service processor, make sure that the applicable device driver and any other required software is installed. For detailed information, see Service processor is unresponsive.
Configuration manager template troubleshooting

This section provides information about problems and workarounds for the configuration manager templates provided by the IBM BladeCenter and System x management plug-in.
Advanced Management Module restarts after applying a plug-in

This problem affects BladeCenter systems that contain an Advanced Management Module.
Problem
When you attempt to connect to an Advanced Management Module immediately after applying one of the following templates, you might be unable to get a connection: v Management Module Network IP Configuration plug-in v Management Module Network SNMP Configuration plug-in v Management Module Ports Configuration plug-in
Explanation
These plug-ins restart the Advanced Management Module after applying a template. Typically, it takes several minutes.
Resolution
To avoid this problem, wait several minutes before connecting to the Advanced Management Module after applying templates of these plug-ins.
Applying or retrieving the SNMP Agent Configuration fails

This problem affects the SNMP Agent Configuration plug-in.
Problem
When you apply or retrieve the SNMP Agent Configuration to or from a target device, the action fails if the target device does not support the SNMP protocol.
Resolution
Make sure that the target device supports the SNMP protocol before you apply or retrieve the SNMP Agent Configuration to or from target device.
Applying the Management Network Configuration fails

This problem affects the Management Network Configuration template
Problem
You create a Management Network Configuration in which you configure an external network. Then, you apply the template to a management module. When you retrieve the current configuration from this management module, you find that the external network that you configured in the template is not retrieved.
157
Explanation
To configure an external network, the blade server must support external networking. If it does not support external networking, the configuration will fail. Note: Only the JS22 blade servers support external networking.
Creating a VLAN configuration fails

This problem affects Switch Module VLAN Configuration templates.
Problem
When creating a VLAN configuration, the creation fails and you receive the following error message:
A VLAN configuration interface ID is incorrect.
Explanation
The Interface number field is labeled as optional. However, the interface number is required for some, but not all, switches. Also, different switches have different supported interface numbers. Some values are supported by one type of switch, but not by another.
Resolution
To resolve this problem, complete the following steps: 1. Make sure you select the correct VLAN configuration template for your switch module. 2. Specify the appropriate value in the Interface number field. Note: If the value for your switch is 0, make sure you type 0 in the field. Do not leave the field blank.
Switch Cisco D-Link Intel Nortel Interface number 0 0 0 1 through 127
Deployment of the IP Pool Configuration template fails on any targeted device

This problem affects the Configuration Manager template called IP Pool Configuration.
Problem
When you deploy a IP Pool Configuration template to any targeted device, the deployment fails.
Explanation
The IP Pool Configuration template provides a pool of IP addresses to other templates, for example Service Processor Network IP Configuration template, that
158
require IP address, gateway, and subnet masks configuration. The affected templates can obtain the IP address, gateway and subnet mask from the IP Pool Configuration templates. Therefore, the IP Pool Configuration template cannot be deployed to any targeted device. Instead, the IP Pool Configuration template assists other templates that need to configure the IP address, gateway, and subnet mask in order to be deployed to their devices.
Resolution
Do not attempt to deploy the IP Pool Configuration template.
Deployment of the User Authentication Configuration template fails on any targeted device
This problem affects the Configuration Manager template called User Authentication Configuration.
Problem
When you deploy a User Authentication Configuration template to any targeted BladeCenter chassis or component, the deployment fails.
Explanation
The User Authentication Configuration template provides the user account information to other templates that require the user name and password configuration. Therefore, the User Authentication Configuration template cannot be deployed to any targeted device. Instead, the User Authentication Configuration template assists other templates that need to configure the user name and password in order to be deployed to their devices.
Resolution
Do not attempt to deploy the User Authentication Configuration template.
The Get an IP address from the IP address pool list is empty

This problem affects any configuration manager template that includes IP address configuration.
Problem
When you open the Create Network IP Configuration window by clicking the Create, Create Like, or Edit buttons, the Get an IP address from the IP address pool list is empty.
Explanation
At least one IP Pool Configuration must be created before the Get an IP address from the IP address pool list can be populated.
159
Resolution
Create an IP Pool Configuration. For information, see Configuring the IP address pool for IBM BladeCenter and System x servers.
Use the specified IP address selection is unavailable

This problem affects the Switch Protocol Configuration template.
Problem
When you create or edit a Switch Protocol Configuration template, the Use the specified IP address selection is not available on the Network page.
Resolution
To resolve this problem, complete the following steps: 1. Click the Login Configuration tab. 2. On the Login Configuration page, determine whether Specify the slot number is set to All. When you specify All, you indicate that the configuration will be applied to multiple switch modules in this chassis and, therefore, multiple IP addresses are required. The Use the specified IP address selection is not valid for multiple IP address selection. 3. Specify a slot number to indicate that the configuration will be applied to one switch. Subsequently, the Use the specified IP address selection is enabled on the Login Configuration page.
Network management troubleshooting

This section provides information for specific problems and workarounds associated with Network Management in the IBM Systems Director environment.
Cannot view configuration of some switches

An error is displayed when attempting to view the configuration of a switch that is not a supported switch.
Problem
Unable to use the System Configuration > Current Configuration task on switch that is not a supported switch to view switch configuration information. When the task is selected, the following error is displayed:
ATKNAV019I There was a problem retrieving the requested data set, and you have been redirected to the home data set. See the logs for details.
Here are more details about the error:

ATKNAV019I: There was a problem retrieving the requested data set, and you have been redirected to the home data set. See the logs for details. Explanation: A data set could not be retrieved using the parameters specified in the Web address. Operator Response: More information about the problem, including error messages, can be found in the file error-log-0.html (and trace-log-0.html if trace is active). The default location of the log files depends on the operating system on which the product is installed. The following list provides the default location associated with each operating system.
160
AIX: /opt/ibm/director/lwi/logs Linux: /opt/ibm/director/lwi/logs Windows: root\lwi\logs, where root is the directory where the product is installed. The default installation directory is c:\Program Files\IBM\Director. If the problem persists, contact your next level of support or your IBM service representative.
Investigation
Check the list of supported hardware for IBM Systems Director Network Management. This problem will occur on switches that are listed as supported for Network Management function but not supported for configuration manager.
Explanation
If you attempt to start a configuration manager task on a switch that is not supported by configuration manager, this error will occur.
Resolution
You cannot use configuration manager to view the configurations of switches that are not supported by configuration manager. To manage configuration of switches not supported by configuration manager, launch a web interface to the switch and use the switch's native configuration interface instead.
Cannot view network interface cards

This problem affects the Network Management function.
Problem
After you install a IBM Systems Director upgrade, inventory collection displays a base board but does not display network interface card (NIC).
Resolution
Network Management in IBM Systems Director can only collect network interface card inventory for NICs that are part of a discovered BladeCenter chassis. This is a known limitation. To collect inventory for NICs that are assigned to a BladeCenter chassis, complete the following steps: 1. Discover the BladeCenter chassis. 2. Request access to the BladeCenter chassis. This step will create a BladeCenter instance and the relationship between them. 3. Repeat the inventory task.
Clicking pie chart on Network Management summary page may not display correct view
On first use, the pie chart on the Network Management summary page may not display the correct view. This problem affects IBM Systems Director version 6.1.1 and later versions.
161
Problem
After installing IBM Systems Director, the first time the user goes to the Network Manager summary page, clicking on the pie chart may simply refresh the current page instead of going to the page displaying the discovered resources in a table. In addition, immediately after a device moves to warning or critical state, clicking the associated status portion of the pie chart may not show the correct view of devices in warning or critical state.
Resolution
Close the Network Management summary page and reopen it. Select the pie chart again to display the discovered resources table or the appropriate view of discovered resources or resources in warning or critical state.
IBM Systems Director Server sends unwanted or unexpected multicast packets

This problem affects users who do not want IBM Systems Director Server to send unwanted or unexpected multicast or broadcast packets to Common Agent managed systems.
Problem
IBM Systems Director Server often uses the service location protocol (SLP) to send multicast packets to and receive multicast packets from registered listeners on the network. If a user does not want to experience or detect unplanned multicast packets, the amount of IBM Systems Director multicast traffic must be reduced.
Resolution
To significantly reduce multicast traffic caused by IBM Systems Director on the network, complete the following steps: CAUTION: Making the following changes might have unintended consequences. For example, after making the following changes, discovery processes (including Getting started discovery and some default discovery profiles) cannot successfully use multicast or broadcast to discover resources. 1. On the IBM Systems Director Server, make the following edits to install_root\data\slp.prop, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
active.da.discovery.interval=0 passive.da.discovery=false broadcast=false multicast=false
2. Restart the IBM Systems Director Server. For instructions, see Restarting IBM Systems Director Server. 3. On the Common Agent managed system, create a file called slp.prop under install_root\agent\runtime\agent\subagents\director\ipc\data, where install_root is the root directory of your Common Agent installation. After you create the file, add the following lines:
162
active.da.discovery.interval=0 passive.da.discovery=false broadcast=false multicast=false
4. Stop and restart the Common Agent. v On AIX or Linux, run the following commands:
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh start
v On Windows, run the following commands:

install_root\agent\runtime\agent\bin\endpoint.bat stop install_root\agent\runtime\agent\bin\endpoint.bat start
where install_root is the root directory of your Common Agent installation. v On IBM i, run the following commands:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS) STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
Completing the previous steps significantly reduces IBM Systems Director multicast traffic.
Delay in threshold page reflecting exceeded threshold

When a threshold is exceeded, causing a device to move into warning or critical state, the threshold page may take over a minute to reflect the status of the device. This problem affects the threshold task in IBM Systems Director Network Management.
Problem
When you set a threshold on a monitor, and a device exceeds the threshold, it may take over a minute for the threshold page to reflect the warning or critical state of the device.
Explanation
When a threshold is exceeded, it may take over a minute for the threshold page to reflect the status of the device. The monitor page will correctly reflect the status of the device.
Resolution
Wait for the threshold page to display the correct status, or view the status on the monitors page.
Duplicate network monitor thresholds

Duplicate network monitor thresholds appear in the threshold list.
Problem
When selecting the Threshold link from the Network Management summary page, individual applied threshold monitors may appear twice in the threshold table.
Resolution
Users should ignore the duplicate threshold entries. When one threshold is deleted, the duplicate will also be removed. There is no need for any other action.
163
Offline network interface card reports incorrect status

This problem affects network interface cards that have a bonded interface and are installed on a managed system that is running a Windows operating system.
Problem
A network interface card (NIC) installed on a managed resource that is running a Windows operating system and that has a bonded interface sometimes does not report status correctly. When the NIC cables of both the bonded interfaces are unplugged, the NIC reports a status of "NIC has switched over" instead of "NIC offline." When the same NIC comes back online, the NIC reports a status of "NIC has switched back."
Resolution
This behavior is a known limitation.
IBM Power Systems management

This section provides information about problems for the IBM Power Systems management management plug-in.
Using IBM i resources with an IBM Systems Director Server

This issue affects IBM i systems.
Getting started
1. Decide the level of agent support that is needed on the IBM i system. v Agentless (formerly Level 0) support provides the ability to distribute the IBM Systems Director agent, IBM Systems Director Navigator for IBM i functions, software inventory and IBM Systems Director support for IBM i Group and cumulative program temporary fixes (PTFs). v Platform Agent (formerly Level 1) provides agentless functions, Common Information Model (CIM) events and monitoring, and additional hardware inventory. v IBM Systems Director Common Agent (formerly Level 2) and IBM Systems Director 6.2 Common Agent for IBM i provide agentless and Platform Agent functions. The IBM Systems Director 6.2 Common Agent for IBM i also provides capabilities such as monitoring IBM i message queues and file transfer. 2. After you decide which level of agent is needed, reference the required software and install documentation for the agent. Notes: v Platform Agent support is provided with the IBM i Licensed Program Product (5722UME or 5770UME). v The IBM Systems Director 6.2 Common Agent for IBM i can only be installed on IBM i 6.1 and later releases.
Requesting access to IBM Systems Director 6.2 Common Agent for IBM i
The user id that requests access to an IBM Systems Director 6.2 Common Agent for IBM i must have these special authorities:
164
v v v v v
*ALLOBJ *AUDIT *IOSYSCFG *JOBCTL *SAVSYS
v *SECADM v *SERVICE v *SPLCTL. Those authorities are provided if the userid has USRCLS = *SECOFR and SPCAUT = *USRCLS.
Starting IBM Systems Director services on an IBM i system

1. Install the latest PTFs on the IBM i system. 2. The services that IBM Systems Director Server uses are provided as IBM i TCP services. Use the appropriate STRTCPSVR commands on IBM i to get those started. Refer to IBM i documentation for instructions to configure services to autostart during a system power up. Some of the TCP servers that you might need to start are *SSHD, *SLP, *CIMOM. 3. The agent is started with this command STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS) Note: SSHD, SLP and CIMOM also need to be started.
No IBM Systems Director metrics data displayed for CIM monitors

IBM i CIM monitors use collection services data. For the CIM metrics to have data, collection services needs to be running. There are many ways to start collection services, for example: 1. CFGPFRCOL INTERVAL(5.0) CYCITV(01) 2. ENDPFRCOL 3. STRPFRCOL CYCCOL(*YES)
IBM i resource levels

Table 6. IBM i resource levels
IBM i resource level Agentless (Level 0) Description SSH Supported IBM i releases Any Required IBM i products-(not all inclusive) 57**SC1 base and option 1 (ssh) for the OS version being used. Configure/start v IBM i 6.1 and later: strtcpsvr *sshd v IBM i 5.4 see: OpenSSH
165
Table 6. IBM i resource levels (continued)

IBM i resource level Platform Agent (Level 1) Description SSH, CIM and IBM Systems Director specific registration. This requires SLP. Supported IBM i releases 5.4, 6.1, 7.1 Required IBM i products-(not all inclusive) Level 0 products CIM / Pegasus PTFs: v 5770UME V1R3M0 (i 6.1 and 7.1) v SI39087 or v 5722UME V1R2M0 (i 6.1 and 5.4) v SI39086 SLP (Base OS) PTFs: v i 6.1: 5761SS1 SI39018 SI39017 v i 5.4: 5722SS1 SI39110 SI39033 5.3, 5.4, 6.1 Configure/start v v v v Level 0 started strtcpsvr *slp strtcpsvr *cimom for monitoring, collection must be started : CFGPFRCOL INTERVAL(5.0) CYCITV(01) ENDPFRCOL STRPFRCOL CYCCOL(*YES)
Common Agent (Level 2)
IBM Systems Director 5.2.x and CIM.
v strtcpsvr *director or v 57722DR1 V5R2M2 /qibm/proddata/ (server/agent) PTFs director/bin/twgstart UK45795 v strtcpsvr *cimom UK44786 v 5722DA1 V5R2M2 (agent) PTFs: UK46478 UK46457 57xxJV1 option 6 (java 1.4) v Level 0 products v Level 1 5770UME V1R3M0 v Java 5761JV1 option 11 (Java SE 6 32bit) v Latest HTTP Server PTF Group IBM i 7.1 SF99368 IBM i 6.1 SF99115 v Level 0 started v Level 1 started v STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS) v ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
Common Agent Services (CAS)--IBM i 6.2 Agent
IBM Systems Director 6.2 Common Agent for IBM i
6.1, 7.1
Related information IBM System i and i5/OS Information Center
Remote access troubleshooting

This section provides information about problems and workarounds related to the remote access manager plug-in.
File transfer hangs after management server restart on IBM System x systems
This problem affects the file transfer function when invoked on IBM System x systems. Only the first invocation of file transfer after the installation or a restart of the management server is affected.
Problem
When you try to start the File transfer task using launch in context (as opposed to using the Remote Access Summary page) on an IBM System xsystem, after the installation or restart of the management server, the task will open a File Transfer window with the message 'Loading File system information' on the bottom left side of the window. This task might never complete.
166
Resolution
Close the File Transfer window and then start the task again. It should complete successfully.
Remote command line does not work on a Windows 2003 Platform Agent managed system when invoked as launch in context
Remote command line cannot be used on a Windows 2003 Platform Agent managed system when invoked with launch in context.
Problem
When you try to start the Remote command line task using launch in context (as opposed to using the Remote Access Summary page) on a Windows 2003 Platform Agent managed system, the task will fail with a pop-up with this message 'The Remote command line service has been closed'.
Resolution
Click OK to close the pop-up. The Remote command line task will terminate. Invoke this task using the Remote Access Summary page.
File transfer does not display files with Chinese characters in the file name if these files were transferred with a tool other than IBM Systems Director File transfer
Problem
When you transfer a file whose name contains some Chinese characters, or the whole name consists of Chinese characters, using a tool other the file transfer task of IBM Systems Director, the file name is not listed in the Target File System list of the File Transfer page.
Resolution
Transfer these files using the file transfer task of IBM Systems Director.
An error is displayed when changing the encoding of a file

An error is displayed when changing the encoding of a file from Unicode big endian to UTF-8.
Problem
When using the file transfer task of remote access, select a file from the Source File System or Target File System list. Click Open, and when the file editor comes up, click Options > Change Encoding. If you try to change the encoding from Unicode big endian to UTF-8, the error message 'An error was encountered while loading file. Terminating' is displayed. The encoding of the file is not changed.
167
Resolution
Select a different character encoding that is appropriate for your file. You can also use operating system tools or other applications to change the file encoding.
File transfer does not support certain characters in file names when using the rename function
File transfer does not support these characters in file names: '*', '?', '|' (asterisk, question mark, vertical bar) when the rename function is used.
Problem
If you try to rename a file or directory whose new name contains special characters: '*', '?',or '|' from within the file transfer facility, an error is displayed. The file or directory will not be renamed.
Resolution
Delete all the special characters from the file or the directory name, and then you can rename it successfully.
File transfer does not filter target file system properly

The filtered Target File System list does not refresh automatically.
Problem
When you set the filter field for the Target File System to a value such as: *.log, and drag a file with different suffix, (for example, a file with a name of a.txt or b.txt) from the Source File System to any directory in the Target File System, the dragged file will not always be filtered out. Sometimes the dragged file will be moved to the Target File System. This problem is intermittent.
Resolution
Manually refresh the directory in the Target Files System.
File transfer cannot open a file that contains unprintable characters

File transfer cannot correctly display unprintable characters.
Problem
An error occurs when you open a file that contains unprintable characters, such as object code, in the File Transfer list. The error message: 'An error was encountered while loading file. Terminating.' is displayed.
Resolution
View the file using operating system commands or a file viewing application.
168
File transfer window sometimes hangs

When the file transfer application is launched, sometimes one window is disabled for any input operation. The window is locked.
Problem
The File Transfer window sometimes hangs. This problem is intermittent.
Resolution
If the File Transfer window does not accept any input, you must close the window and restart the file transfer task.
Remote command line prompt on a Windows 2003 Common Agent managed system does not have working scroll bars
This problem affects users of Remote command line on a Windows 2003 Common Agent managed system.
Problem
The Remote command line prompt on a Windows 2003 Common Agent managed system may not have working scroll bars. In addition, you might be unable to resize the window, which will disable you from being able to return to the prompt after you type the first command. Finally, the entire Remote command prompt window and the launched task window can freeze.
Explanation
Windows 2003, 64 bit edition, contains an Enhanced Security Configuration to prevent use of the operating system as a console.
Resolution
You can disable the Enhanced Security Configuration by following these steps: 1. Click Start > Control Panel > Add or Remove Programs. 2. In the Navigation area, click Add/Remove Windows Components. 3. In the Windows Components Wizard, use the scroll bar to locate the Internet Explorer Enhanced Security Configuration. 4. Uncheck the box next to it and complete the removal process.
System z management
This section provides information about problems for the IBM System z management plug-in.
Access state is Unknown for z/VM host operating system

(IBM Systems Director 6.1 only.) This problem affects z/VM host operating systems. This problem is resolved in IBM Systems Director version 6.1.1.
169
Problem
After discovering the z/VM host operating system, you view it in IBM Systems Director and notice that the access state of the z/VM host operating system is Unknown.
Explanation
This problem is a known limitation of IBM Systems Director. After you discover an IBM z/VM Manageability Access Point Agent, which is running on a Linux operating system, IBM Systems Director creates the z/VM host operating system and discovers its associated virtual servers. The access state of the z/VM host operating system is displayed as Unknown. However, processes such as discovery and inventory collection are not adversely affected. Inventory is collected through the Linux operating system, rather than through the z/VM host operating system (which indicates an Unknown access state). Therefore, the inventory collection task is performed as expected.
Discovery of z/VM managed resources does not function correctly

This problem affects managed resources hosted by the z/VM operating system and occurs during the discovery process.
Problem
You cannot discover any managed resources that are hosted by the z/VM operating system.
Explanation
The problem might be occurring for one of the following reasons: v An unsupported version of Linux is installed on the z/VM manageability access point v A firewall is blocking communication to the IBM z/VM Manageability Access Point Agent v The Platform Agent or IBM z/VM Manageability Access Point Agent is not installed v The CIM server is not running v The z/VM Systems Management API server is not working or not able to communicate with the IBM z/VM Manageability Access Point Agent v z/VM Systems Management API user IDs are not running
Resolution
To resolve this problem, perform the following steps on the managed system: 1. Ensure that you have installed a supported version of Linux on the z/VM manageability access point. For more information, see Operating systems supported by IBM Systems Director 6.1. 2. Ensure that there are no firewall problems. 3. Ensure that Platform Agent is running by issuing the following set of commands that is appropriate for the level of Platform Agent that is installed:
170
Platform Agent 6.2.1 /opt/ibm/icc/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grep Linux_ComputerSystem_instance /opt/ibm/icc/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grep IBMzVM_HostComputerSystem_instance Platform Agent 5.20.3x /opt/ibm/icc/cimom/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grep Linux_ComputerSystem_instance /opt/ibm/icc/cimom/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grep IBMzVM_HostComputerSystem_instance Restart Platform Agent by stopping and then starting it: a. Stop Platform Agent by typing the following commands and then pressing Enter:
/etc/init.d/cimserverd stop /etc/init.d/tier1slpinst stop /etc/init.d/cimlistenerd stop /etc/init.d/ibmsa stop (Platform Agent 5.20.3x only) /etc/init.d/paslpd stop (Platform Agent 6.2.1 only)
b. Start Platform Agent by typing the following commands and then pressing Enter:
/etc/init.d/ibmsa start (Platform Agent 5.20.3x only) /etc/init.d/paslpd start (Platform Agent 6.2.1 only) /etc/init.d/cimlistenerd start /etc/init.d/tier1slpinst start /etc/init.d/cimserverd start
If Platform Agent is not running, go to Step 5. If Platform Agent is running, go to Step 6 on page 172. 4. Ensure that the SLP daemon is running by issuing the following command that is appropriate for the level of Platform Agent that is installed: Platform Agent 6.2.1 /opt/ibm/icc/bin/slptool -u ipaddr_of_agent findsrvs service:management-software.IBM:platform-agent where ipaddr_of_agent is the IP address of the Platform Agent system. Platform Agent 5.20.3x /opt/ibm/icc/slp/bin/slp_query --type=service:* --address=ipaddr_of_agent where ipaddr_of_agent is the IP address of the Platform Agent system. 5. Ensure that Platform Agent is installed by completing the following steps: a. Check for the version.lv1 file in the location that corresponds to the level of Platform Agent that is installed: v Platform Agent 6.2.1: /opt/ibm/platform v Platform Agent 5.20.3x: /opt/ibm/director If Platform Agent is not installed, go to Step 5b. If Platform Agent is installed, go to Step 6 on page 172. b. Install Platform Agent and IBM z/VM Manageability Access Point Agent. Then, try to discover the managed resources again. For installation instructions, see Installing Platform Agent and Installing IBM z/VM Manageability Access Point Agent. If you are still unable to discover the managed resource, go to Step 7 on page 172.
171
6. Ensure that IBM z/VM Manageability Access Point Agent is installed successfully by checking for the version.zvmmap file in the /opt/ibm/zvmmap directory. Note: An alternate method of ensuring that IBM z/VM Manageability Access Point Agent is installed is to run the following command that is appropriate for the level of Platform Agent that is installed: Platform Agent 6.2.1 /opt/ibm/icc/bin/cimcli ei IBMzVM_HostOperatingSystem Platform Agent 5.20.3x /opt/ibm/icc/cimom/bin/cimcli ei IBMzVM_HostOperatingSystem If IBM z/VM Manageability Access Point Agent is not installed, install it and try to discover the managed resources again. For installation instructions, see Installing IBM z/VM Manageability Access Point Agent. If you are still unable to discover the managed resource, go to Step 7. 7. Ensure that z/VM Systems Management API server is working. Type the following command and press Enter:
/opt/ibm/zvmmap/bin/testSMAPI
If the z/VM Systems Management API server is working, you will see results that are similar to the following output:
Obtaining system information from SMAPI. zVM version: z/VM Version 5 Release 4.0, service level 0000 (64-bit) Obtaining directory information from SMAPI The directory for OPERATOR contains 13 records
An error message might be displayed. Read the following information to identify possible error messages and how to resolve them:
172
Table 7. Error messages and resolutions Error message Unable to obtain socket Resolution Ensure that the kernel module af_iucv was properly loaded into the Linux system. To check if it was loaded, run the following command: lsmod |grep af If the module was properly loaded, running the command will produce results similar to the following output: af_iucv 150624 0 iucv 111192 1 af_iucv If you do not receive this output, the module was not loaded and you need to perform the following steps: 1. Run the following command to load the module: modprobe af_iucv 2. Configure the module to load every time the system is booted: v For SUSE Linux: a. Open the following file: /etc/sysconfig/kernel b. Look for the following line: MODULES_LOADED_ON_BOOT="" c. Change the line as follows: MODULES_LOADED_ON_BOOT="af_iucv" v For Red Hat Linux: a. Create the following file: /etc/rc.modules b. Add the following line to the file: modprobe af_iucv c. Set the following permission to the file: chmod +x /etc/rc.modules
Connection refused
Ensure that the z/VM Systems Management API file VSMWORK1 AUTHLIST contains the Linux IBM z/VM Manageability Access Point Agent user ID. Options: v Wait until the z/VM Systems Management API server is less busy, and try the task again. v Ensure that the IUCV ALLOW statement is in the VSMREQIU directory. v Go to Step 8a on page 174.
Connection retry exceeded
Other errors
Go to Step 8a on page 174.
173
If you are unable to resolve the errors, contact your IBM service representative. If the z/VM Systems Management API server is still not working, go to Step 8 8. Ensure that the z/VM Systems Management API user IDs are running on the z/VM system. a. Restart the z/VM Systems Management API server by completing the following steps: 1) Force off VSMWORK1. Log on to the z/VM host as MAINT, type the following command, and press Enter:
#CP FORCE VSMWORK1
2) Log VSMWORK1 back on. Type the following command and press Enter:
#CP XAUTOLOG VSMWORK1
VSMWORK1 will force off and automatically log on the other servers it needs. b. Run a query to determine whether the required z/VM Systems Management API user IDs are running. Log on to the z/VM host as MAINT, type the following command, and press Enter:
QUERY NAMES
Verify that the following z/VM Systems Management API user IDs are running: v v v v v VSMREQIN - DSC VSMREQIU - DSC VSMWORK1 - DSC VSMWORK2 - DSC VSMWORK3 - DSC
v DATAMOVE - DSC (if you are using the DirMaint functions) v DIRMAINT - DSC (if you are using the DirMaint functions) If the z/VM Systems Management API user IDs are not running, contact your IBM service representative. For more information about the z/VM Systems Management API and DirMaint, see the following documentation: v z/VM Systems Management API documentation: Systems Management Application Programming SC24-6122 v DirMaint documentation: Directory Maintenance Facility Commands Reference SC24-6133 Directory Maintenance Facility Messages GC24-6134 Directory Maintenance Facility Tailoring and Administration Guide SC24-6135
Incorrect values are displayed for CPU Utilization and Process Count on Linux on System z
This problem affects the Linux on System z that has Platform Agent installed.
Problem
When you view the Common CIM Monitors for the Linux on System z that has Platform Agent installed, you notice that the values for CPU utilization and process count are not correct.
174
Explanation
This problem is a known limitation of IBM Systems Director.
Job status for inventory collection on IBM z/VM Manageability Access Point Agent is Complete with Errors
This problem affects the IBM z/VM Manageability Access Point Agent during inventory collection.
Problem
When you use the Collect Inventory task to collect inventory data on the IBM z/VM Manageability Access Point Agent, the job status for inventory collection is Complete with Errors.
Explanation
The Collect Inventory task for the IBM z/VM Manageability Access Point Agent can take 40 minutes or more to complete. However, the Collect Inventory task times out after 20 minutes, the default timeout value.
Resolution
Increase the timeout value for the Inventory Collection task, by completing the following steps: 1. Edit the following file:
<director_install>/lwi/conf/overrides/USMIKernel.properties
where <director_install> is the IBM Systems Director installation directory. 2. Append the following line to the end of the file:
perf.extended.discovery.timeout=180
The timeout value that you specify depends on the number of Linux on System z resources that have been discovered during system discovery. In most cases, 180 minutes is a sufficient length of time to collect inventory on the resources associated with the IBM z/VM Manageability Access Point Agent. 3. Restart the IBM Systems Director Server.
Network adapter status for the Linux on System z is Unconfigured

This problem affects the Linux on System z that has either Platform Agent or Common Agent installed, and has an HiperSockets LAN IP address.
Problem
You discover, request access to, and collect inventory from, a Linux on System z. The Linux on System z has either Platform Agent or Common Agent installed, and has an HiperSockets LAN IP address. You view the network configuration for the Linux on System z in IBM Systems Director. The status for All Network Adapters is Unconfigured. However, you know that the HiperSockets LAN IP address has been configured.
175
Explanation
This problem is a known limitation of IBM Systems Director. IBM Systems Director does not recognize the Hipersockets LAN IP address as a configured network adapter.
Storage systems management troubleshooting

This section provides information about problems and workarounds related to the storage systems management plug-in.
Cannot start an IBM DS Storage Manager with version later than 10.6.x.x
Only version 10.60.g5.16 or earlier is supported. If you already downloaded a later version of IBM DS Storage Manager and cannot start it, try this procedure.
Resolution
For later versions of IBM DS Storage Manager, the binary names might have changed. Try the following steps to solve this problem: On Microsoft Windows systems: 1. Navigate to the directory that contains the file DS Storage Manager 10 Client.exe and run the command Copy "DS Storage Manager 10 Client.exe" "Storage Manager 10 Client.exe". 2. Navigate to the directory that contains the file DS Storage Manager 10 Client.lax and run the command Copy "DS Storage Manager 10 Client.lax" "Storage Manager 10 Client.lax". On Linux or AIX systems: 1. Create a link from /opt/IBM_DS to /opt/IBM_DS4000 by using this command:
ln -sf /opt/IBM_DS /opt/IBM_DS4000
2. Create a link from /opt/IBM_DS4000/client/SMclient to /usr/bin/SMclient by using this command:

ln -sf /opt/IBM_DS4000/client/SMclient /usr/bin/SMclient
Could not install or uninstall on a Microsoft Windows system

If you try to install or uninstall Storage Control and it fails, you need to perform some cleanup before you can retry the task.
Problem
Because there was a problem with the install or uninstall, some files and settings that should be removed were left on your system. You cannot retry the install until you follow the manual cleanup steps that follow.
Resolution
Follow these steps to remove the files and settings: 1. Using the Windows Services panel, stop the Device Server service. The service is named IBM WebSphere Application Server V6.1 - DeviceServer. a. To access the Services panel, click Start > Control Panel > Administrative Tools > Services.
176
b. In the right pane, browse for IBM WebSphere Application Server V6.1 DeviceServer. Right click the name of the service and select Stop. Note: If Stop is greyed out, it is already stopped. 2. Delete these folders: v C:\Program Files\Common Files\InstallShield\Universal\IBM-TPC v C:\Program Files\IBM\TPC 3. Delete the specified keys from the Windows registry. Important: Be careful when editing the registry. If you use the Registry Editor incorrectly, you can cause serious problems, possibly requiring you to reinstall the operating system. a. Start the Registry Editor: 1) Click Start > Run
2) Enter the command regedit, then click OK. b. When the Registry Editor window opens, click Edit > Find. c. The Find panel opens. Ensure that only Keys is selected. Deselect every other checkbox. d. In the Find what field, enter IBMWAS61Service - DeviceServer and click Find Next. Delete the key. Important: Only delete the exact key that is specified. Do not delete any keys that begin with LEGACY. Close the Registry Editor. e. Use the DB2 Control Panel to drop the TPC database. 1) Open a DB2 command line window. Go to Start > Programs > IBM DB2 > Command Line Tools > Command Line Processor. 2) Enter list database directory. If the database TPCDB is listed, then enter drop database TPCDB. 3) Close the command line window. f. Remove the specified users from the system: 1) Go to Start > Settings > Control Panel > Administrative Tools > ComputerManagement. 2) The Computer Management window opens. In the left pane, under Computer Management (Local), expand Local Users and Groups. Click Users. The users are listed in the right pane. 3) Delete these users: v TSRMSrvn, where n can be any number; usually it is 1. v TPCUser. 4) Close the Computer Management window and the Administrative Tools window. g. Restart the system.
Could not install or uninstall on a Linux or AIX system

If you try to install or uninstall Storage Control and it fails, you need to perform some cleanup before you can retry the task.
177
Problem
Because there was a problem with the install or uninstall, some files and settings that should be removed were left on your system. You cannot retry the install until you follow the manual cleanup steps that follow.
Resolution
Follow these steps to remove the files and settings: 1. Stop the device server. a. On AIX, run /opt/IBM/TPC/device/bin/aix/stopTPCF.sh. b. On Linux, run /opt/IBM/TPC/device/bin/linux/stopTPCF.sh. 2. To clean up the product registry , delete the following directory: /etc/Tivoli/TSRM. 3. To clean up the installation registry, delete the appropriate directory: v For AIX, delete /usr/lib/objrepos/InstallShield/Universal/IBM-TPC. v For Linux, delete /root/InstallShield/Universal/IBM-TPC. 4. AIX only: Remove the subsystem: a. Run this command: lssrc -a to determine the name of the Storage Control subsystem. The name will be TSRMsrn, where n can be any number; usually it is 1. b. Run this command: rmssys -s TSRMsrn, where n is the value determined previously. run this command: 5. Drop the appropriate database: a. Log in as a DB2 user, such as db2inst1. b. Run this command to drop the database: db2 drop db database_name TPCDB is the default name. 6. Delete the TPC installation directory: /opt/IBM/TPC/.
Cannot access PlatformAgentSubagent SMI-S for IBM SAS RAID Controller Module
IBM Systems Director 6.2 Platform Agent has been installed, but now you cannot access PlatformAgentSubagent SMI-S for IBM SAS RAID Controller Module.
Problem
You try to discover IBM SAS RAID Controller Module SMI-S provider by using SLP discovery or SMI-S discovery. The request to unlock fails.
Resolution
Ensure that the installed versions of Platform Agent and the SMI-S provider are compatible. The following combinations are compatible: v IBM Systems Director Platform Agent 6.2 and IBM SAS RAID Controler Module SMI-S Provider R2.1 (version 4.xx) v IBM Systems Director Platform Agent Core Services 5.20.31 and IBM SAS RAID Controler Module SMI-S Provider R1 (version 2.99)
178
DS 3000/4000/5000 proxy provider configuration causes provider to fail

When trying to add a device into a DS device that is Chromium (06.60) and 06.12 firmware (CFW) versions, the target DS3000/4000/5000 provider might crash.
Problem
When configuring the DS3000/4000/5000 provider by adding a device, the user can input both the primary and secondary controller's IP addresses. When the target device is of the firmware level specified above, entering both values will crash the provider and it will need to be manually restarted.
Resolution
When adding a DS device into a provider, only specify the primary controller's IP address. Do not specify the secondary controller's IP address.
This problem is only observed when the DS device is Chromium (06.60) and 06.12 firmware (CFW) versions. For DS devices at other firmware levels, this problem will not happen.
Unable to discover an SMI-S provider

You have installed an SMI-S Provider and IBM Systems Director is not discovering it.
Problem
In the System Discovery screen, you insert the IP Address of an SMI-S Provider on your network and wait until discovery finishes. At the end of the process, IBM Systems Director does not find your system.
Explanation
SMI-S Discovery uses the Service Location Protocol to find SMI-S systems on your network. If a system is not discovered, this can be caused by the following: v SLP service not working correctly on the SMI-S provider. v IBM Systems Director and SMI-S provider are on different subnetworks.
Resolution
If the SLP service is not working correctly, try restarting the SMI-S provider or using the ICC SLP command line tools to perform queries of your SMI-S provider. Also try restarting the system that hosts the SMI-S provider. To restart the SMI-S provider, restart the provider service on the resource, which varies by provider. To run an SLP query by hand, run this command for Linux: Platform Agent 6.2.1
/opt/ibm/icc/bin/slptool options
179
Where options are the options that you specify based on the information in the slptool command topic. Platform Agent 5.20.3x
/opt/ibm/icc/slp/bin/slp_query
or this command for Windows: C:\Program Files\Common Files\IBM\ICC\slp\bin\slp_query.exe on your IBM Systems Director Server with service-type = service:wbem and the IP address of your resource. If the SMI-S provider and the IBM Systems Director Server are on different subnetworks, you can v Establish a direct connection to the provider. v Use Advanced Systems Discovery and use an SLP Directory Agent to serve as a proxy for SLP requests on a network. If you choose to use an SLP Directory Agent, you need to configure it in the network where the SMI-S provider resides.
After requesting access to an SMI-S provider, no storage systems or switches are displayed
You discovered a system that you know is one of your SMI-S providers, and after requesting access, no storage systems are available.
Problem
You discover and request access to a system that has an SMI-S provider installed, yet no new storage systems are displayed. This is normally caused by a Discovery failure.
Investigation
If the system you unlocked is not in the Storage Systems > SMI-S Providers group, IBM Systems Director did not recognize it as a system having an SMI-S provider.
Resolution
See the topic 'Unable to discover an SMI-S provider' for storage discovery troubleshooting. If you choose to use a Directory Agent, you need to configure it in the network where the SMI-S provider resides.
SMI-S provider configuration fails to add a storage device

When configuring an SMI-S provider, storage devices are not added.
Problem
When you try to add a storage device with an SMI-S provider, the operation fails after clicking OK on the Add Storage Devices page.
180
The storage system will not be added, and you will stay on the same page, where a error message is displayed describing the problem that occurred. This problem is independent of the web browser that you use.
Resolution
Complete the following steps: 1. Verify that the storage system is online. The IBM Systems Director Web interface might display the storage device as being online, but a change in this status is not reflected immediately in the IBM Systems Director Web interface. You can do this by selecting the storage system and clicking Actions > Verify connection. 2. If you are using manual mode, verify that the IP addresses for both the primary and secondary controllers are correct. You can try running a ping command for the controllers, or check if the controllers can be resolved from your server system. 3. If you are using manual mode and you typed the correct credentials but the IP addresses for the controllers were incorrect, you will receive this error message: "An unexpected error occurred while performing the selected operation". Verify that the IP addresses for the controllers are correct. 4. Another reason for this failure is that you might be providing the wrong credentials for the storage device. Check the error message displayed in the IBM Systems Director Web interface, and if you find that it is a security-related problem, confirm that you have access to the storage system with the given credentials, and that they are typed correctly. 5. Verify that the storage device you are trying to add can be managed by the SMI-S provider that you have chosen. SMI-S provider configuration will run only for SMI-S SAS RAID Controller Module providers. 6. If the SMI-S provider is hosted by a Windows system, make sure that the selected protocol is http. You select the protocol in the Discovery Profile wizard for the SMI-S provider. The SMI-S provider for Windows does not support https protocol properly.
SMI-S provider configuration fails to remove a storage device

When configuring an SMI-S provider, storage devices are not removed.
Problem
This is from the SMI-S Provider Configuration page, which is launched when you select a system that is an SMI-S provider. When you try to remove a storage device controlled by the SMI-S provider, the operation fails after selecting the device and clicking Actions > Remove. The storage system will not be removed, and you will remain on the same IBM Systems Director Web interface page where an error message is displayed describing the problem. This problem is independent of the web browser that you use.
Resolution
Complete the following steps:
181
1. Verify that the storage system is online. The IBM Systems Director Web interface might display the storage device as being online, but a change in this status is not reflected immediately in the IBM Systems Director Web interface. You can do this by selecting the storage system and clicking Actions > Verify connection. 2. See if the storage device has been removed by other means, but it has not been reflected in the IBM Systems Director Web interface. From the same Verify Connection task mentioned in the previous step, check the Query for Vital Properties box. If the storage device has been removed, the next time it will not be displayed n the IBM Systems Director Web interface. 3. In order to remove devices attached to a RAID controller, information about the RAID controllers is required. If you never collected inventory on the device, you must do so in order to delete it.
Installing the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module on additional systems completes with errors
The agent install of the PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0 (either Windows or Linux), competes with errors.
Problem
The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module has one of these operating-system dependent names: v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0 Linux v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0 Windows Due to a limitation of the agent installation task, you are permitted to install this SMI-S provider on a system that does not have a Platform Agent managed system installed. However, this configuration will not work properly.
Explanation
For the configuration to function properly, IBM Director 5.20.3 Level-1 agent must be on the system prior to running the agent installation task for the PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0. However, due to a limitation of the agent installation task, there is no way to prevent the user from install it to a system that does not have minimum of IBM Director 5.20.3 Level-1 agent.
Resolution
Install IBM Director 5.2.0.3 Level-1 agent prior to running the agent installation task for the PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0.
Storage events not being displayed in the event log

Your storage device is failing, but IBM Systems Director is not displaying events.
182
Problem
You know that your storage device is having problems, yet you see no events in IBM Systems Director.
Resolution
In order to receive events in IBM Systems Director, you need to have discovered the SMI-S provider and have it in an unlock state. Event subscriptions occasionally become obsolete on the provider. If this happens, you should select the provider and click Actions > Security > Verify Connection. Make sure that the Query Vital Properties check box is selected, and click Verify. The subscriptions should be updated periodically, but this is a quick way of updating them.
Unable to display a topology map of a SAN

There are discovered devices from a SAN, but you cannot see the links between them.
Problem
In IBM Systems Director, you have discovered all of your SAN devices, yet when you select the topology perspective, you do not see the links.
Resolution
In order to see a topology map, complete the following steps: 1. Run the collect inventory task for your systems, servers, storage arrays, and storage switches. 2. Request access to all of the above items. 3. Collect inventory on all of the above items. 4. Select either a switch, storage array, or server. 5. Click Actions > Topology Perspective > SAN Topology. 6. The topology map should now be displayed.
The SAN configuration profile is not updated when a blade changed in an IBM BladeCentersystem
This problem affects SAN configuration with IBM BladeCenter systems.
Problem
After you deploy a SAN configuration template, then remove or replace a blade to an IBM BladeCenter chassis, the SAN configuration profile of this blade is not updated on storage related to this chassis.
Explanation
The deploy function of SAN configuration template to IBM BladeCenter system functions to get the SAN configuration profile of blades and set the target blade. If you did not selected the blade in the SAN configuration template and then deploy the template, the SAN configuration profile will not be saved, and SAN configuration profile of the blade will not be replaced.
183
Resolution
Make sure that you selected all appropriate blade, and deployed the SAN configuration template to the IBM BladeCenter system.
Replace and remap task fails with an IBM BladeCenter S SAS RAID Controller Module for a blade whose host name is more than twelve characters in length
The replace and remap task fails with an IBM BladeCenter S SAS RAID Controller Module for a blade whose host name is more than twelve characters in length. Replace and remap cannot create a host in the IBM BladeCenter S SAS RAID Controller Module after inserting the new blade.
Problem
When you use the replace and remap task on an IBM BladeCenter S SAS RAID Controller Module and the blade's resource name is more then twelve characters, the host cannot be created.
Explanation
There is a twelve character name limit in SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module. It is currently a firmware limitation. The physical limit in firmware is 24 characters, where the first twelve are available for user definition. They are limited to alphanumeric characters and the underscore character.
Resolution
Use this command to change blade's host name to twelve or fewer characters: 1. Change the current directory to install_directory\bin\, where install_directory is the location where IBM Systems Director is installed. 2. Issue this command: smcli chsys A Name=host name -n blades display name where host name is a new host name that is twelve or fewer characters consisting of letters, numbers, or underscores, and where blades display name is the current value of the blade's host name.
iSCSI configuration accepts incomplete IPV4 format addresses

Why IPV4 address formats such as '1', '1.', '1.2', and '1.2.3' are valid in iSCSI configuration.
Problem
When you create an iSCSI configuration template, you must provide some IP addresses. If you type an incomplete string by mistake, you do not receive an error message.
184
Investigation
Textual representation of IPV4 address used as input to methods takes one of the following forms: d.d.d.d d.d.d d.d d When a four part address is specified, each is interpreted as a byte of data and assigned, from left to right, to the four bytes of an IPV4 address. When a three part address is specified, the rightmost part is interpreted as a 16 bit quantity and placed in the rightmost two bytes of an IPV4 address. This makes the three part address format convenient for specifying Class B network addresses as 9.186.96. When a two part address is specified, the rightmost part is interpreted as a 24 bit quantity and placed in the rightmost three bytes of an IPV4 address. This makes the two part address format convenient for specifying Class A network addresses as 9.186. When an address consisting of only one part is specified, the value is stored directly in the network address without any byte rearrangement.
Resolution
Ensure that you are using these IPV4 address formats correctly.
Deploy of a SAS Zone configuration failed on an IBM BladeCenter after access to the Advanced Management Module
This problem affects SAS zone configuration in IBM BladeCenter systems.
Problem
When you try to deploy a SAS Zone configuration template to an IBM BladeCenter chassis, the deploy fails, although access request to the Advanced Management Module of the IBM BladeCenter chassis is successful. After discovery and access request to the IBM BladeCenter chassis are done, there will be a SAS switch displayed in the resource group. The SAS Zone configuration template is supposed to apply to a IBM BladeCenter chassis or SAS switch.
Resolution
Request access to the SAS switch first when you want to deploy a SAS Zone configuration template, or configuration plan that contains a SAS Zone configuration template, to the SAS switch.
No predefined SAS zone configuration when there is only one SAS switch, and it is on I/O Module 4 on an IBM BladeCenter S system
185
Problem
When you create a SAS Zone configuration template with just one SAS switch on I/O Module 4, a warning message is issued: DNZCP2726E - I/O Module 4 does not support predefined configuration. In a single SAS module configuration, the SAS module must be placed in I/O Module 3 in order to access predefined configurations. You will see that there is no predefined SAS zone configuration stored in the configuration template.
Resolution
The predefined SAS zone configuration is saved in the SAS switch and is set for the recommended configuration. On IBM BladeCenter S systems, we suggest that if you have only one SAS switch, to put it on I/O Module 3. There will be no predefined SAS zone configuration for one SAS switch on I/O Module 4.
Mismatched configuration of two SAS switches on an IBM BladeCenter S system

Problem
If you have two SAS switches on an IBM BladeCenter S system, and they have different SAS zone configurations, there will be a warning message about the different uses of I/O Module 3 and I/O Module 4. The message is: DNZCP2724E The active zones for I/O Modules 3 and 4 are different. A mismatched configuration can cause unexpected results.
Resolution
On IBM BladeCenter S systems, there are two storage modules. If there are two SAS switches on the chassis, each SAS switch will connect to one storage module. The two SAS switches will work together to provide the SAS zone configuration for blades to external ports or disks. We suggest that have the same SAS zone configuration on two SAS switches on one IBM BladeCenter S system.
Cannot view available storages when creating a logical volume in offline mode
This problem affects storage provisioning using configuration templates.
Problem
When you try to view logical volumes using the Storage provisioning configuration template, you might want to choose the target storage system by yourself, as opposed to allowing IBM Systems Director to make the choice. But sometimes, IBM Systems Director fails to list available storage, so there are no storage records in the Storage provisioning table.
Resolution
If you want to choose the storage by yourself, you must discover the storage first. Create a discovery profile using the following values:
186
v On the Profile Properties page, select Operating System as the resource type and All as the resource subtype. v On the Protocol Selection page, select Storage Management Initiative Specification (SMI-S) Discovery. v On the SMI-S Configuration page, select Direct connection, select the appropriate hardware type, and specify the IP address of the storage provider. After saving the discovery profile, run system discovery using the profile, then unlock the storage provider. If you see that the storage is shown in the Navigate Resources page after unlocking the provider, you can then select this storage in the Storage provisioning configuration template.
Cannot get some properties of storage devices

This problem affects storage provisioning using configuration templates.
Problem
When you try to choose logical volume allocation by yourself, you can see some properties of the storage listed in the Logical Volumes page. But sometimes, some properties are missing. So you do not see any value in some of the table cells.
Resolution
If you want to get more detailed information, such as the free capacity and connection type for the storage, you need to collect inventory on the storage.
SAS Port panel launched from SAS switch is not correct

When a Serial Attached SCSI (SAS) switch is selected, and SAS port information is displayed, it is found to be incorrect.
Problem
This scenario might cause a problem: 1. Collect inventory to ensure that the SAS switch is accessible. 2. Click System Configuration > SAS Ports. 3. The SAS Ports panel is displayed, but the information is not correct.
Resolution
These are suggested actions: v Make sure that you are not blocked by a firewall, by issuing this command. telnet IRC host
where IRC host is the host name or IP address of the IRC host. When prompted, enter the correct user ID and password for the firewall. v Clear your browser cache. Refer to the documentation for the browser that you are using for instructions.
187
IBM BladeCenter S SAS RAID Controller Module menu tasks are not displayed for an attached storage array (storage subsystem)
IBM BladeCenter S SAS RAID Controller Module menu tasks are not displayed on the storage array menus.
Problem
After discovering the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module using SLP discovery, appropriate menus are not displayed. The problem can be seen with this sequence of actions: 1. Perform SLP discovery of the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module. 2. Unlock this SMI-S provider. 3. Right click on an attached storage resource. 4. Select System Configuration. 5. No menus for managing this resource are displayed.
Resolution
Make sure that the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module is in the same subnet as the management server. If not, use SMI-S discovery instead of SLP discovery for this SMI-S provider.
IBM BladeCenter S SAS RAID Controller Module menu tasks fail for an attached storage array (storage subsystem)
IBM BladeCenter S SAS RAID Controller Module menu tasks are displayed on the storage array, but they do not work properly.
Problem
After discovering the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module using SLP discovery or SMI-S discovery, appropriate menus are displayed, but they have an incorrect domain. The problem can be seen with this sequence of actions: 1. Perform SLP or SMI-S discovery of the SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module. 2. Unlock this SMI-S provider. 3. 4. 5. 6. Right click on an attached storage resource. Select System Configuration or System Status and Health. Select any storage-related task. An incorrect domain page is displayed.
Resolution
Make sure that the following discovery process is performed: 1. Discover and unlock the SMI-S provider. 2. Discover and unlock the IBM BladeCenter chassis. 3. Discover and unlock all SAS switches attached to the IBM BladeCenter chassis.
188
A previously supported IBM BladeCenter S SAS RAID Controller Module is no longer supported after installing IBM Systems Director 6.1.1.
An IBM BladeCenter S SAS RAID Controller Module that was discovered and supported by IBM Systems Director 6.1 is no longer supported after installing IBM Systems Director 6.1.1 Platform Agent.
Problem
After installing IBM Systems Director 6.1.1, then manually installing Platform Agent 6.1.1, a BladeCenter S SAS RAID Controller Module that was discovered and supported by IBM Systems Director 6.1 is no longer supported. Installing IBM Systems Director 6.1.1 Platform Agent may cause the provider to stop working, causing a loss of support for the BladeCenter S SAS RAID Controller Module.
Resolution
Manage the BladeCenter S SAS RAID Controller Module by using a provider that you install on a remote system.
Cannot create RAID 0 level pools on certain LSI IRC devices

Using the Create Volume wizard to create a RAID 0 level pool on an Integrated RAID Controller (IRC) device results in an error.
Problem
When using the Create Volume wizard, creating a pool that contains only one (1) RAID 0 disk for an LSI 106x IRC device fails with an error.
Resolution
The firmware for LSI 106x devices does not support creating a RAID 0 pool with only one (1) drive. To create a RAID 0 pool for an LSI 106x IRC device, you must specify at least two (2) drives to create a pool.
Capacity information is not correct for storage devices

The capacity information displayed on the Local Storage row of the Storage Management Summary page is not correct.
Problem
The Local Storage row on the Storage Management Summary page is not correct. The raw capacity, available capacity, and usable capacity show a default value of 0 because of this limitation. The other rows (Network storage and IBM BladeCenter storage) are correct.
Resolution
Use operating system utilities or storage management applications to determine usable and available storage capacity.
189
When managing an Integrated RAID Controller (IRC), incorrect controller device information is displayed.
Sometimes, when managing an Integrated RAID Controller (IRC) device, the information shown is incorrect.
Problem
When managing an Integrated RAID Controller (IRC) device, the interface displays incorrect information.
Resolution
To ensure that the Storage Manager displays correct information for the IRC device you are managing, verify that you have installed the latest driver levels for that IRC. For more information about the latest drivers and firmware levels, access the Web site for the device manufacturer.
Some menu options are missing for an Integrated RAID Controller (IRC) device
Previously visible options under the menus System Configuration and System Status and Health for an Integrated RAID Controller (IRC) device no longer appear.
Problem
The following options that appeared in the System Configuration or System Status and Health menu for IBM Systems Director 6.1 for an Integrated RAID Controller (IRC) device no longer appear in IBM Systems Director 6.1.1. v System Configuration > Volumes v System Status and Health > Physical View v System Status and Health > Device Log v System Status and Health > Collect Support Data
Resolution
IBM Systems Director 6.1.1 does not support certain tasks for IRC devices, and the previously specified menu options associated with those tasks are no longer available.
Some ServeRAID MR controller devices not supported by IBM Systems Director 6.1.1
After installing IBM Systems Director 6.1.1 Platform Agent, some RAID devices are no longer supported.
Problem
After installing IBM Systems Director 6.1.1 Platform Agent, some RAID controller devices do not send alerts or health status and do not gather inventory.
190
Resolution
Use a combination of an IBM Systems Director agent and the supported ServeRAID manager extension from the following table.
Table 8. IBM Systems Director agent and ServeRAID manager extension combinations that support specific RAID controllers IBM Director Core Services Agent, version 5.20.31 Yes1 IBM Director Core Services Agent, version 5.20.3 Yes1 IBM Director Level 2 Agent. version 5.20.3 Yes2 IBM Director Level 2 Agent, version 5.20.2 Yes3
RAID controller IBM ServeRAID 4H/4M/4L/ 4Mx/4Lx
Platform Agent 6.1.1 and later Not supported
IBM Not ServeRAID 5i supported IBM ServeRAID 6i/6i+/6M IBM ServeRAID 7k/7t IBM ServeRAID 7e/8e Not supported Not supported Not supported
Yes1 Yes1
Yes1 Yes1
Yes2 Yes2
Yes3 Yes3
Yes1
Yes1
Yes2
Yes3
Yes1
Yes1
Yes2
Yes3
IBM Not ServeRAID supported 8k/8k-l/8i/8s LSI 1020/1030 Not supported
Yes1
Yes1
Yes2
Yes3
Yes1
Yes1
Yes2
Yes3
1. Requires ServeRAID 9.0 Extension for Core Services 2. Requires ServeRAID 9.0 Extension for Director Agent 3. Requires ServeRAID 8.40 Extension for Director Agent
Remote Supervisor Adaptor and Remote Supervisor Adaptor-II devices not supported by IBM Systems Director 6.1.1
Cannot use IBM Systems Director 6.1.1 Platform Agent to manage IBMRemote Supervisor Adaptor or IBM Remote Supervisor Adaptor II devices.
Problem
After installing IBM Systems Director 6.1.1 Platform Agent, you can not manage IBM Remote Supervisor Adaptor or IBM Remote Supervisor Adaptor II devices.
Resolution
IBM Systems Director 6.1.1 Platform Agent does not support IBM Remote Supervisor Adaptor or IBM Remote Supervisor Adaptor II devices. IBM Remote Supervisor Adaptor and IBM Remote Supervisor Adaptor II devices work only with IBM Director Core Services, version 5.20.31.
191
Storage panel or Long Running Tasks panel fails when managing ServeRAIDMR Controller or Integrated RAID Controller (IRC) devices
After updating to IBM Systems Director 6.1.1 and working to manage either an Integrated RAID Controller (IRC) or a ServeRAID MR controller, certain panels fail and then always show an error.
Problem
After updating to IBM Systems Director 6.1.1, when managing an IRC device or a ServeRAID MR Controller device, certain panels fail and then always show an error. v When managing an IRC device, launching the Storage panel fails, which causes an error message to always display on the panel. v When managing a ServeRAID MR Controller device, launching the Storage panel or the Long Running Tasks panel fails, which causes an error message to always display on the panel.
Resolution
The system configuration tasks for ServeRAID MR devices and IRC devices do not work with older providers, even when using IBMDirector Core Services agent, version 5.20.31. However, tasks associated with basic discovery, inventory, and alerts do work correctly.
A pool with a RAID level of RAID10 on a ServeRAID MR Controller device can have a maximum of four drives
Volume pools with a RAID level of RAID10 created for ServeRAID MR Controller devices cannot contain more than four drives.
Problem
Using the Create Volume Wizard to create a pool with a RAID level of RAID10 for a ServeRAID MR Controller device fails when you specify more than four (4) disk drives.
Resolution
It is a known limitation that a pool with a RAID level of RAID10 for a ServeRAID MR device can contain a maximum of four disk drives.
Using tasks available on Storage panel for Integrated RAID Controller (IRC) devices results in errors
After installing IBM Systems Director 6.1.1, some tasks on the Storage panel for Integrated RAID Controller (IRC) devices result in errors.
Problem
After installing IBM Systems Director 6.1.1 Platform Agent, using most of the tasks available on the Storage panel results in errors.
192
Resolution
The Storage panel in IBM Systems Director 6.1.1 supports only two tasks for IRC devices. Use only the following tasks that are supported for IRC devices: Create Volumes and Delete Volume, both of which appear on the Volume tab. The Integrated RAID Controller does not support many other advanced functions available for Storage Management in IBM Systems Director 6.1.1, including the following: v On the Disk Drives tab Assign Global Spare Clear Foreign Configuration Initialize Locate Drives Unassign Global Hot Spare v On the Pool tab Locate Drives Pool Properties Unassign a Dedicated Spare v On the Volume tab Locate Drives Volume Properties Expect to encounter errors if you use the previously specified functions for Integrated RAID Controller devices.
Controller error when starting a task

When launching a task against an AR/IR host with CAS agent installed, you might get one of these controller errors: GWMAR1020E Unable to retrieve controller information associated with host ip_address... GWMAR0102W No managed controller is available...
Problem
The credential was not added to CIM Remote service access point (RSAP) correctly.
Resolution
Follow these steps to add the credential to CIM RSAP manually: 1. Right-click the AR/IR host and select Security > Configure Access 2. From the Configure Access page, right-click the RSAP that uses CIM access and select Credential. 3. A new table opens. Click Configure Credentials in the upper left corner of the table. The Configure Credential Wizard starts. 4. Use the wizard to create the User ID and Password credential. 5. After completing the wizard, start the task again.
193
System status and health

This section provides information for specific problems and workarounds associated with the System status and health task.
Automation command does not show the interactive program window

This problem affects machines running the Windows 2008 operating system.
Problem
An interactive program is any program that is launched in a user interface window and requires user intervention, for example notepad.exe. When you try to use the command automation task to run an interactive program on Windows 2008, the program is not launched as expected. However, the process related to that interactive program is still is displayed in the Windows task manager.
Explanation
The command automation task is intended for command line automation, which includes only those processes that terminate by themselves within a specified time period and require no user intervention. It is possible, though not supported, to use the command automation task to launch interactive programs. However, this is not even possible on Windows 2008. Windows 2008 has a new set of security considerations that come into effect and cause the interactive program window to not appear, though the process is listed as active and running in the Windows task manager. The processes are launched in the service session (session ID 0), which is never a desktop session.
Resolution
Use a method other than the command automation task to launch interactive programs.
Cannot add selected resources to a monitor view

This problem affects monitoring on any resource.
Problem
When you select resources on the Create View page to add to a monitor view, Add is not activated and you cannot add the selected resources to your view.
Explanation
Add is activated only when an item that can be monitored, such as CPU Utilization, is selected. If you select any items that cannot be monitored, Add remains deactivated.
Resolution
Select a different resource to monitor.
194
Error is encountered while loading shared libraries

This problem affects the Process Management task. It occurs on only those managed resources that run Linux.
Problem
When running the Process Management task or any action that uses Linux operating-system commands, you might receive the following error message:
error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
Explanation
This error results from Java setting the environment variable LD_ASSUME_KERNEL, which is incompatible with commands launched from the Java environment. This problem affects several commands, including the following commands: v ps v top v pgrep v pstree
Resolution
Set the LD_ASSUME_KERNEL variable to an empty value as part of the action. For example, when running ps as a Process Management action, instead of issuing the command ps -ef, use LD_ASSUME_KERNEL=;ps -ef.
Power Systems server IVM events appear in the event log with incomplete Event Text and Source fields
(IBM Systems Director 6.1 only) This problem affects Power Systems. This problem is resolved in IBM Systems Director version 6.1.1.
Problem
Most events that are received from the IVM appear in the event log with the value No Text in the Event Text field, and some of these events also have the value -1 in the Source field.
Resolution
Click on No Text to open the event properties panel. Here you can view the actual event type in the Component Type field and the actual source of the event in the Source field.
Events are not created immediately when a threshold is exceeded

This problem affects monitoring and thresholds on any resource.
Problem
When the value of a monitor goes above the threshold level that you specified, an event is not immediately created.
195
Explanation
By default, an event is generated only after the value of the monitor is above the threshold for five minutes.
Resolution
Change the minimum duration for the threshold to the desired value.
Incorrect events reported for NICs that have a teaming configuration of active-standby
The problem affects the reporting of events for managed resources where teaming (or bonding) for any active network interface card (NIC) is configured as active-standby. The problem is limited to NICs installed in managed systems that are running any supported Windows operating system.
Problem
When a network interface card (NIC) in a managed system has a teaming configuration of active-standby, IBM Systems Director incorrectly reports some events for that NIC. Note: Usually, an NIC is configured as active-standby only when the managed resource contains more than one active NIC.
Explanation
Currently NIC teaming supports only an active-active configuration. Because NIC teaming does not support an active-standby configuration, associated events are limited to SwitchOver and SwitchBack. Look for NIC teaming events in the Systems Director Event Log for the managed server (out-of-band) and in the Service Processor Console web user interface.
Table 9. Expected and reported events for NIC with teaming set to active-standby NIC teaming Primary = Failed Secondary = Active Symptom Primary NIC fails; teaming switches from primary NIC to secondary NIC Expected event* SwitchOver Reported event SwitchOver
Primary = Active Primary NIC comes Secondary = Standby online, teaming switches from secondary NIC to primary NIC Primary = Active Secondary = Failed Standby NIC fails
SwitchBack
SwitchBack
Offline Online
SwitchOver SwitchBack
Primary = Active Standby NIC comes Secondary = Standby online
* A network interface card with a teaming configuration of active-active correctly reports the expected NIC events.
196
Resolution
The problem identified in this topic is a known limitation for NICs with a teaming configuration of active-standby.
Monitored memory values are too high

This problem affects IBM Systems Director for 6.1.0 and earlier when monitoring memory on AIX and Linux on Power Systems.
Problem
When using IBM Systems Director for 6.1.0 and earlier, the monitoring values for memory, which are accompanied by the MB metric, are too high.
Explanation
The values are displayed in bytes, not in MB, as indicated by the metric.
Resolution
Divide the value by 1048576 (the equivalent of 1024 squared) to calculate the value in MB instead of bytes. Upgrading to IBM Systems Director 6.1.1 or later resolves this problem.
Monitored disk space values are too low

(IBM Systems Director 6.1 only) This problem affects monitoring of disk space on AIX . This problem is resolved in IBM Systems Director version 6.1.1.
Problem
The monitoring values for disk space, which are accompanied by the MB metric, are too low for AIX agents.
Explanation
The value displayed is actually the size for the / file system, not the whole disk.
Resolution
Use another method to determine the disk space.
Monitoring tasks are not displayed in the Actions menu

Problem
When you select a resource on the Navigate Resources page and click Actions, the monitoring tasks are not listed.
Explanation
Monitoring actions are available for only those resources that are running Platform Agent or Common Agent and that are, at a minimum, online and accessible. There are also other monitoring restrictions that might apply based on the resource type
197
or relationships. If a system cannot be monitored for any reason, the monitoring options will not appear in the Actions menu.
Resolution
Ensure that the resource is online and accessible. If you still cannot access monitoring actions for the selected resource, other restrictions exist and you will need to investigate them individually.
Monitors are not listed for the selected resource

Problem
When you click Show Monitors on the Monitors page, the Monitor View page displays the statement No Data Available and no monitors are listed.
Explanation
There are many possible explanations for this specific problem, three of which are most likely: v The resource cannot be monitored. Monitoring actions are available for only those resources that are running Platform Agent or Common Agent and that are, at a minimum, online and accessible. There are also other monitoring restrictions that might apply based on the resource type or relationships. If a system cannot be monitored for any reason, no monitors will be listed for it. v The selected monitor view is not supported for the selected resource. Therefore, no monitors are available. For example, many monitors are not available for various 5.20.x agents, so those monitors will display No Data Available. v The selected resource has gone offline or another critical event has occurred
Resolution
First, ensure that the resource has the ability to be monitored. If the resource can be monitored, implement the following potential solutions to cover both possible explanations for this specific problem: v Create a monitor view for the resource. v View the properties of the resource to ensure that it has not gone offline or reported another critical event. v Ensure that you have the latest version of the agent. If the resource cannot be monitored, or if none of the suggested monitoring solutions works, use another method to collect the data.
No data available error for AIX and VIOS monitors

This problem affects AIX monitors and VIOS monitors when inspecting AIX managed systems or VIOS managed systems.
Problem
Using an AIX monitor or VIOS monitor in IBM Systems Director Server to inspect an AIX managed or VIOS managed system causes No Data Available to display in all monitor entries.
198
Explanation
The AIX monitor and VIOS monitor tasks in IBM Systems Director require that the AIX managed systems and VIOS managed systems be running specific versions of the operating system or common agent.
Resolution
To resolve the problem with the AIX monitor, make sure that you have one of the following installed on the AIX managed system: v AIX 53 TL10 or earlier, with Common Agent 6.1.2 reinstalled v AIX 53 TL11 or later v AIX 61 TL03 or earlier, with Common Agent 6.1.2 reinstalled v AIX 61 TL04 or later To resolve the problem with the VIOS monitor, make sure that you have one of the following installed on the VIOS managed system: v VIOS 2.1.0.1, VIOS 2.1.0.10, or VIOS 2.1.1 with Common Agent 6.1.2 reinstalled v VIOS 2.1.2 or later
Predictive Failure Analysis events not reported for System x3755 M3 servers
The problem affects the reporting of Predictive Failure Analysis events from managed IBM System x3755 M3 servers.
Problem
Platform Agent fails to report Predictive Failure Analysis events for processors or DIMMs that occur on x3755 M3 servers. Because the specified events are not reported, you cannot see any of those events in the event log for the operating system of the managed server.
Explanation
Because x3755 M3 servers use a non-IBM baseboard management controller (BMC), the following situations occur: v The BMC firmware on a x3755 M3 server does not detect the Predictive Failure Analysis sensors for processors and DIMMs v IBM IPMI firmware commands do not work on x3755 M3 servers Platform Agent cannot report the specified events unless detection of and support for Predictive Failure Analysis sensors and support for Predictive Failure Analysis sensor events is added to the non-IBM BMCs.
Resolution
The failure to report Predictive Failure Analysis events is a known limitation that is specific only to System x3755 M3 servers. You can view Predictive Failure Analysis events in the IBM Systems Director event log for the managed x3755 server (out-of-band). Additionally, you can use the service processor console web interface to view the events.
199
Resource is not returned by the browse function

Problem
The resource that you want to monitor is not displayed in the context chooser when you click Browse on the Monitors page.
Explanation
Monitoring actions are available for only those resources that are running Platform Agent or Common Agent and that are, at a minimum, online and accessible. There are also other monitoring restrictions that might apply based on the resource type or relationships. If a system cannot be monitored for any reason, it will not show up in the list of monitors when you browse and the monitoring options will not appear in the Actions menu. Note: If nothing happens when you click Browse, there are no resources that match the criteria for monitoring.
Resolution
Ensure that the resource is online and accessible. If the resource is still not displayed when you click Browse, other restrictions exist and you will need to investigate them individually.
Resources are encountering problems that you need to monitor and manage
This problem can affect any resource.
Problem
You encounter problems with your resources and aren't sure how to gather information about, monitor, or manage the problems.
Explanation
Any resource can encounter problems. IBM Systems Director provides a set of tools that you can use to monitor and manage the status and health of resources in your environment from a single interface. Use these tools to monitor and manage problems that your resources are encountering.
Resolution
See the related information about problem status set entries and the error log.
Save changes confirmation window is invoked despite no changes

This problem affects Microsoft Internet Explorer and Mozilla Firefox browsers when running IBM Systems Director 6.1.2 and earlier.
200
Problem
When you try to close the process management launched task, even if you have not made any changes, you are prompted to save your changes before the window closes.
Resolution
Electing to save or not save yields the same result, so just pick one and click the appropriate button to close the confirmation window and the launched task window.
Two microprocessor monitor resources are displayed when only one microprocessor exists
This problem affects the Resource Monitor task on managed resources running Windows with Hyper-Threading capability.
Problem
When you view the microprocessor monitor resources after you run the Resource Monitors task on managed resources running Windows with Hyper-Threading capability, resource attributes for two microprocessors are displayed despite the fact that the resource contains only one microprocessor.
Explanation
This problem occurs when Hyper-Threading is enabled for the microprocessor. If Hyper-Threading is enabled, the Resource Monitors task displays two microprocessor monitor resources when only one microprocessor exists. The Resource Monitor task draws data from the operating system, and the operating system interprets a single Hyper-Threaded microprocessor as two logical microprocessors.
Update manager troubleshooting

This section provides information about problems and workarounds related to the update manager plug-in.
Unable to import updates from network mounted directories

Update Manager is unable to import updates from network mounted directories in Windows.
Problem
When using the importupd command or Import Updates task, if the path given is for a network mounted directory, the message The specified file {path} was not found. is displayed and no updates are imported.
Explanation
The IBM Director Server service runs as a local Windows service, which does not have access to network shares mounted in user space. All IBM Systems Director command-line interface (smcli) commands are actually performed by the running server and not by smcli.
201
Resolution
Copy the updates to a local drive and import the updates from there.
Update installation tasks never complete

New update installation tasks remain in a running state.
Problem
Following an improper or incomplete shutdown or failure of the IBM Systems Director Server, attempts to install updates to a legacy 5.x Director agent on the target system might fail if a previous installation was in process at the time of the shutdown or failure. The new installation process might remain in a running state.
Resolution
Restart the Director agent on the target system and attempt to perform the installation tasks again.
Getting Started wizard for update manager indicates that some systems are not supported
After selecting systems in the Getting Started wizard, a message is displayed indicating that some of the systems are not supported.
Problem
After selecting system in the update manager Getting Started Wizard, message 'ATKUPD065W The default update types do not currently support all of the selected systems' is displayed.
Investigation
For each affected system that should be supported by IBM Systems Director, ensure that the system is unlocked and that software inventory has been collected for it. Some delay can occur between inventory being collected and processed, so wait some time before trying the Getting Started wizard again.
Explanation
Updates are supported only for certain operating systems and IBM hardware platforms. The affected systems might not be one of these supported platforms. When there is no update support currently available for any aspect of a given system, the Getting Started wizard indicates that IBM Systems Director does not support updating the system.
Resolution
Review the list of supported platforms and operating systems.
A system cannot be chosen from the Getting Started, Install, or Install staging wizards
A particular system cannot be chosen in the update manager Getting Started, Install staging, or Install wizards.
202
Problem
When using the Getting Started, Install staging, and Install wizards, the Systems page does not allow selection and addition of a particular system.
Resolution
Ensure that the system is unlocked, and that software inventory has been collected for it.
IBM BladeCenter Settings tab is not displayed

This problem affects the Settings function when used to specify settings for IBM BladeCenter systems.
Problem
The BladeCenter Settings tab is missing from the Release Management > Updates > Settings page, but other Settings tabs such as Connection, Location, and so forth, are displayed.
Investigation
In order for the BladeCenter Settings tab to be displayed, the management server must have been discovered. This should happen automatically, but there are situations where it does not.
Resolution
Use Inventory > System Discovery to discover the management server. The management server might also need to be unlocked.
When specifying IBM BladeCenter Settings, messages about empty fields are displayed
This problem appears when using the Settings tab to specify settings for IBM BladeCenter systems.
Problem
Saving changes to the BladeCenter Settings tab fails because required fields have not been filled out. Error message: DNZUPX053E: The field field name must not be empty is issued.
Explanation
The BladeCenter Settings tab is divided into two sections: TFTP settings and FTP settings. This is the validation: v If the Do not use a TFTP server option is selected, no additional TFTP data is required. v If the Use the management server as a TFTP server option is selected, no additional TFTP data is required. v If the Use system option is selected for TFTP: The Use system field is required. The Network Interface field is required.
203
The TFTP root directory field is required. v If the Do not use an FTP server option is selected, no additional FTP data is required. v If the Use system option is selected for FTP: The Use system field is required. The Network Interface field is required. The FTP user home directory field is required. The User name field is required. The Password field is required.
Resolution
Examine the above Explanation and complete all required fields.
When specifying IBM BladeCenter Settings, messages about incorrect syntax are displayed
This problem affects the Settings function when used to specify settings for IBM BladeCenter systems.
Problem
Saving changes to the BladeCenter Settings tab fails because incorrect syntax or data has been used. Error message: DNZUPX054E: The field field name has incorrect syntax is issued.
Explanation
Syntax validations are done for the following fields: v For the TFTP root directory: If the TFTP server is running on a Linux system, the value of this field must start with '/' (forward slash). If the TFTP server is running on a Windows system, the value of this field must start with a letter (A through Z or a through z) followed by ':\' (colon then backward slash). v For the FTP user home directory: If the FTP server is running on a Linux system, the value of this field must start with '/' (forward slash). If the FTP server is running on a Windows system, the value of this field must start with a letter ('A' through 'Z' or 'a' through 'z') followed by ':\' (colon then backward slash).
Resolution
Examine the above Explanation and complete all required fields.
Error occurred trying to start the TFTP server used for IBM BladeCenter and System x updates
This problem occurs when trying to start the TFTP server used to obtain updates for IBM BladeCenter and System x systems.
204
Problem
Update manager for IBM BladeCenter and System x provides a TFTP server embedded within the management server to aid in the distribution of update files to certain IBM BladeCenter devices. This TFTP server is started when the user selects Use the management server as a TFTP server in the BladeCenter Settings tab. You might receive error message DNZUPX056E: An error occurred trying to start the TFTP server on the management server.
Explanation
There are several reasons for an error when starting the TFTP server. The most common cause is that the port used by the TFTP server is already in use by another application or process (most likely a different TFTP server).
Resolution
Check if port number 69 is in use by another application. If that is the case, shut down that application and try to restart the TFTP server by selecting the Use the management server as a TFTP server option on the BladeCenter Settings page. Alternatively, an external TFTP server can be used by specifying the Use System option, and specifying the TFTP root directory and Relative path to updates fields.
Most platforms provide a command, such as netstat on Windows and Linux, to check the availability of the ports.
Compliance is not accurate for a system

Update manager incorrectly indicates that a system is out of compliance.
Problem
A system is shown as being in compliance when the administrator knows it to be out of compliance, or a system is shown as being out of compliance after an install has been performed that should have brought it into compliance.
Investigation
Ensure that the system is unlocked and the latest software inventory has been collected. After collection, the inventory data can take some time to be fully processed, at which point the compliance information should be accurate. Processing of inventory occurs at a default time interval of ten minutes, so you should wait at least this long for inventory processing to start. The manner in which compliance is configured also needs to be considered. v If a dynamic update group is being used, only updates determined to be needed by the system will cause a out-of-compliance indication. v If a static update group is being used, only updates that are applicable to the system will cause an out-of-compliance indication. In either of these cases, the inventory data must be current and processed in order for accurate results to be displayed.
205
Resolution
Unlock the system and ensure that the latest inventory has been collected.
Changes to a compliance policy's groups do not immediately result in issues

Membership changes to update or system groups within a compliance policy do not cause compliance issues to be immediately created.
Problem
When a compliance policy is created using a system group or an update group, and membership changes occur to either group, compliance issues might not be immediately created. Common scenarios include: discovering a system that is automatically added to a dynamic system group, or obtaining new updates that are then automatically added to a dynamic update group.
Explanation
Compliance policies evaluate group membership at periodic intervals. The default interval for the poll time is every ten minutes, and is specified with the GroupMembershipPollerTimeInMinutes. property. This time can be modified using the update.properties properties file, which has this path: \lwi\runtime\core\workspace\.metadata\.plugins\com.ibm.usmi.services.updates Increasing this time could provide performance benefits, while decreasing this time could provide performance degradation.
Resolution
Ensure that adequate time has elapsed for the group membership changes to be processed.
Check for updates does not display on the system's menu

The Check for updates menu item does not appear on a system's menu.
Problem
The Check for updates, Show installed updates, and Show needed updates menu items are not displayed on a system's menu.
Resolution
Ensure that the system is unlocked, and that the current software inventory has been collected.
Check for updates obtains information on more updates than expected

The Check for updates task downloads updates for more update types than expected.
206
Problem
When checking for updates on a system, more types of updates are downloaded than are appropriate for the system.
Resolution
When a check for updates is run for a system or system group, the updates specified in the compliance policy are checked as well. If a system belongs to a system group, any compliance policy associated with the system group will be inherited by the system, and used during its check for updates. These additional checks may cause additional update information to be downloaded.
Unable to find update compliance task logs

The log files produced by the update compliance policies for a given system are not found with the log files for tasks run on that system. The update compliance task cannot be found on the Task Management > Active and Scheduled Jobs page.
Explanation
The update compliance task is run automatically when changes happen such as the import or acquisition of new updates, the completion of inventory collection on a system, or changes to the membership of a group in a compliance policy. Since the task is run automatically by update manager as opposed to being scheduled by a user, it does not appear in the Active and Scheduled Jobs page.
Resolution
The compliance task information, including it's logs, can be viewed from the system that compliance was run against, by following these steps: 1. Click Navigate Resources > All Systems group. 2. Choose the appropriate system. 3. Click Actions > Properties > Applied Activities. 4. Choose the Update Compliance link of interest to view its status, history, logs, and so forth.
Compliance status is not accurate for IBM BladeCenter I/O modules

This problem affects IBM BladeCenter updates.
Problem
I/O modules (for example, IBM BladeCenter Switches and Pass-through Modules) can be marked as compliant, when in reality, critical updates need to be installed.
Resolution
Follow these steps: 1. Ensure that the IBM BladeCenter system containing the I/O module is discovered, unlocked, and online.
207
2. Unlock each I/O module separately. Access to the IBM BladeCenter's Management Module is not sufficient. 3. As with all other compliance checks, ensure that inventory is collected on each I/O module.
Update compliance is not refreshed when adding a nested group to a compliance policy
Nested update groups and system groups for update manager do not inherit compliance policies.
Problem
A compliance policy is defined for a static System group or Update group. Another group is later added to the static group defined in the compliance policy. Compliance status is not refreshed for the systems or updates in the new, nested group.
Explanation
A System group or Update group can be added to a static group of the same type, but nested groups will not inherit the compliance policy of any parent group they are included in. For example, if a compliance policy is made up of a static Update group that contains updates and other Update groups, only the updates of the group in the policy will be validated for compliance to the systems in the same policy. Anything within the nested Update group will not be considered for validation of the compliance policy.
Resolution
Create a separate compliance policy for nested System groups and Update groups.
Multiple compliance policy entries result in multiple compliance issues for the same system
Adding more than one policy criteria entry may result in more than one issue for the system.
Problem
A compliance policy is set up for a single system using two criteria, perhaps a group and a single update. This can result in there being two compliance issues, two results, and two recommendations created for the same system.
Explanation
Multiple compliance policy criteria can be added for a system. If the system is not compliant with the criteria, each may result in an issue and recommendation being created for that system. An example is if a compliance policy is added for a dynamic update group, such as All Updates, which contains updates, and later another policy criteria is added for a single update. On the Issues and Recommendations panel, two systems will be listed as non-compliant, but they will be the same system.
208
Resolution
Use one compliance policy per system, or combine the policies into a single criteria using, for example, a static update group.
When a compliance check entry is added to a compliance policy for a system group, compliance issues are shown for both the operating system and the server
Even though they are the same physical system, operating systems and computer systems are treated as separate entities when listing compliance issues.
Problem
A compliance policy is set up for a system group containing the server and operating system for a single physical system. This can result in there being two compliance issues, two results, and two recommendations created for what appears to be the same system.
Explanation
Because both operating systems and servers of computer systems are considered by IBM Systems Director to be resources, update manager compliance testing treats them as separate entities. There may be two systems shown as non-compliant even though they both represent the same physical system.
Resolution
Create the policy on either the operating system or the system, and use a static group to group all operating systems. Resolving the compliance issue for one resource will resolve it for both systems.
Compliance issues not resolved after successful install of updates

This problem affects users of Update manager.
Problem
Compliance issues remain unresolved after successfully installing updates.
Investigation
First, check that the automatic inventory collection completed successfully against the out-of-compliance systems on which the updates were installed. If the inventory collection completed successfully, check to see if the compliance job failed. You can do this by following these steps: 1. In the IBM Systems Director Web interface navigation area, click System Status and Health. 2. Click Event log. 3. Type Compliance in the search box and click Search. 4. Look for a Compliance Failed event associated with the out-of-compliance system's property page.
209
You can also look for a failed Update Compliance job activation in the out-of-compliance system's property page. Follow these steps: 1. In the IBM Systems Director Web interface navigation area, click Navigate Resources. 2. Select the All Systems group. 3. Navigate to the out-of-compliance system and click on it to view its properties. 4. Select the Applied Activities tab for the system. 5. Click the latest Update Compliance job activation to view its status. 6. Select the Logs tab. 7. 7. Look for any activations that completed with errors. If any are found, inspect the job log for a failure. An example error might look like this:
Wed Apr 29 11:30:30 PDT 2009-Level:50-MEID:0--MSG: ATKUPD553E Task "UpdateComplianceTask" has failed with error: ATKUPD550E An error occurred while performing compliance checks on resources. Error: ATKUPD581W Compliance processing encountered an exception: "ATKUPD585W Compliance processing encountered Resource Caching Exception: "cdlwcsi15.cn.ibm.com" ." .
Explanation
This error can happen when the IBM Systems Director Server's CPU is being maximized and multiple compliance jobs are running against the same system.
Resolution
Collect inventory against the out-of-compliance system to activate compliance. When the Update Compliance job completes successfully, the compliance issues should be resolved.
Update compliance issue remains unresolved after installing Director 5.20.x agent updates on Linux systems
In inventory, the version property of the Director 5.20.x agent does not get refreshed properly after an update, which means that the compliance issue remains unresolved.
Problem
After installing a Director 5.20.x agent update on a Linux system, the version property does not get updated properly. The update installation completes successfully, but the version information does not get updated correctly, which causes the update manager compliance policy to report that the update still needs to be applied.
Resolution
To resolve this issue: 1. Restart Director 5.20.x agent on the target system. 2. Collect inventory for the target system. 3. If the problem persists: a. Remove the target system from the IBM Systems Director Server. b. Discover the target system again. c. Collect inventory for the target system.
210
Running out disk space during update download can cause random application errors and server startup errors
This problem can occur when downloading updates that consume a large amount of disk space.
Problem
Updates may consume a large amount of space in the file system, typically /opt or c:/, where IBM Systems Director is installed. Some updates, such as Hardware Management Console and AIX , can consume gigabytes of disk space when they are downloaded or installed. Running out of free space can cause random application failures and problems starting the IBM Systems Director Server. This consideration is especially important for AIX systems.
Resolution
Ensure that adequate free space exists in the file system where the updates are being downloaded. The amount of free disk space must be greater than the Maximum disk space to use value in the update Settings function. The maximum disk space to use value can be checked by clicking Release Management > Updates > Settings, and then checking the value on the Locations tab.
The default maximum disk space to use for updates is 10 gigabytes. Ensure that this amount of disk space or more is free on the file system where IBM Systems Director is installed.
Download of updates fails due to proxy server connection issues

Test connection, check for update, or download tasks fail on systems connected to the Internet through a proxy server.
Problem
When you try to test the connection to the Fix Service Provider, or check for updates, or download updates and the task fails because the function cannot connect to the Internet using the proxy server (this only applies to client systems that use a proxy server to connect to the Internet).
Resolution
There are several prerequisites that must be met in order to use a proxy server to connect to IBM and download updates. Ensure that all of the following prerequisites are met: v Configure a system in your environment to act as a proxy server. Verify that the system is working as a proxy server by making sure that you can access the Internet through ports 80 (HTTP) and 443 (HTTPS). The firewall and proxy server must permit bidirectional communication through these ports. v Configure the proxy server for SSL tunneling. v Determine whether you want to require authentication for the proxy server. Note that only Basic authentication is supported. If you configure your proxy server to use Digest or NTLM authentication, you will be unable to connect to IBM.
211
v On the Updates page, locate the Settings Tasks group and click Getting started. v Click the Connections tab to display the Connections page. Check the Use HTTP proxy server check box. v Type the proxy server information in the Host name or IP address and Port fields. v Click Test Connection to test the connection settings that you have selected.
The IP addresses and ports used to contact the Fix Service Provider are defined in files that reside in this directory: install_root\lwi\runtime\core\workspace\.metadata\.plugins\ com.ibm.usmi.services.updates.acquisition.eccbase\ecc\config\ where install_root is the root directory of your IBM Systems Director installation. The serviceProviderIBMLocationDefinition.xml will be used if it exists. Otherwise ,the serviceProviderIBM.xml that ships with IBM Systems Director will be used to attempt to download a recent version of the serviceProviderIBMLocationDefinition.xml file.
Download of updates fails with an error of download size exceeded

This problem occurs when the Maximum disk space to use setting is set to an amount that is too small to accommodate the updates you want to download.
Problem
When you try to download updates from IBM, the download fails and the task history log contains message 'ATKUPD812E Cannot download updates because the updates library would exceed its configured maximum size of size MB.'
Resolution
This problem occurs when the Maximum disk space to use setting is set to an amount that is smaller than the size of the updates you want to download. To correct the problem, complete these steps: 1. On the Updates page, locate the Settings Tasks group and click Change settings. 2. Click the Location tab to display the Location page. 3. The storage location for updates cannot be changed, but it is displayed for reference. 4. Increase the Maximum disk space to use value so that it is it is large enough to accommodate the size of the updates to be downloaded. This value is in Megabytes (MB). 5. If you cannot increase this setting due to a lack of disk space on your system, narrow down your download criteria so that the size of the download is smaller.
212
Download or Import task fails to add an IBM System x or IBM BladeCenter update
The download or import tasks do not retrieve an expected update for an IBM System x or IBM BladeCenter system.
Problem
IBM System x and IBM BladeCenter updates must have their descriptor files converted to the standard format used by update manager. This conversion can fail under certain circumstances, which could keep this update from being acquired by update manager. Potential causes of failures include: 1. The IBM System x descriptor file has syntax errors. 2. The update is too outdated to work with IBM Systems Director 6.1. Any updates described with schema versions earlier than 3.0 are considered to be outdated. 3. Certain categories and types of IBM System x updates are not supported. This file contains a list of unsupported pairs in the property CATEGORY_TYPE_NOT_SUPPORTED: install_root/data/UpdateManager_x_bc.properties where install_root is the root directory of your IBM Systems Director installation. 4. The update is too outdated to apply to newer hardware. For example, some older IBM BladeCenter switch updates do not indicate support for the IBM BladeCenter S chassis. This is because the update's descriptor was generated before the IBM BladeCenter S chassis was released. (This applies only to the download tasks.)
Resolution
In general, the best solution is to contact your service provider and alert them of a possible problem with an update descriptor file. However, in cases where you are familiar with the IBM System x descriptor file, you can attempt to fix a syntax error and retry an import task. As an example, this descriptor contains an error:
<PROPERTY NAME="ibmSchemaVersion" TYPE="string"> 3.0 <VALUE></VALUE> </PROPERTY>
Notice that the value 3.0 has been placed outside of the <VALUE></VALUE> tags. To fix the syntax error, modify the descriptor like this, and retry the task.
<PROPERTY NAME="ibmSchemaVersion" TYPE="string"> <VALUE> 3.0</VALUE> </PROPERTY>
Conversion logs are maintained to keep track of errors during processing. The logs are generated in directory
213
install_root/lwi/logs/cimtosdd/ where install_root is the root directory of your IBM Systems Director installation. A separate log file is created each time that an error occurs, with the following name: updateIdsystem timestamp.log Examine these logs for error messages and take appropriate action.
Unable to import update

One or more updates cannot be imported because the local management server resource was not found in the database.
Problem
When you try to import an update using the importupd command, you receive an error message (ATKUSC308E) saying that a resource representing the local management server cannot be found in the database.
Resolution
Ensure that the local system has been discovered, unlocked, and software inventory has been collected on it. To verify that the local system has been discovered, run the lssys command.
See the troubleshooting topics for system discovery and access if you are unable to discover or request access to your local system.
Install and Installation staging tasks not available for an update

The install and installation staging actions are not available for an update.
Problem
When viewing a list of updates, the install or installation staging actions are either not available or not selectable for a particular update.
Resolution
This will happen when the update is not known to be appropriate for any discovered system. If you know that the update should be appropriate for a discovered system, ensure that the system's software inventory has been collected and is current. Once inventory is collected, the processing of the inventory can still take several minutes. The menu actions will not be available until after the inventory has been processed.
214
Update installation staging does not transfer all members of an update group
This affects installation staging of updates to remotely accessed systems.
Problem
When using the installation staging task (or install task) to transfer updates to the remote system, in some cases the update might not be applicable to the system. This could happen if an update group is selected for installation staging that contains updates that are not applicable to the system. If the installation staging task is run with updates that do not apply to the system, it will skip the update and log the following message in the task history log.
ATKUPD617W The update update_ID is not applicable to the system system_name. The update will not be staged for installation to this system.
Investigation
To determine if the staging of updates were skipped for this reason, examine the task history log. The task history log is found in the Task Management > Active and Scheduled Jobs page in the IBM Systems Director Web interface. Click on the failed task, and then click the Logs tab. Right click on the failed activation, and then choose Show Logs. Examine the logs for this error, ATKUPD617W, or similar messages.
Resolution
If the update should apply to the target system, collect inventory on the target system again. This will cause update processing to run to determine which updates apply to the system.
IBM BladeCenter Install and Installation Staging tasks fail when using an FTP or TFTP server
This problem occurs when using the FTP or TFTP server for the install or installation staging tasks for IBM System x and IBM BladeCenter systems.
Problem
Errors occur when attempting to perform installation staging tasks using FTP or TFTP servers. Installation staging is the task that copies installable firmware files to the FTP or TFTP server. The installation staging task can be explicitly requested, or it may happen implicitly before an install task.
Resolution
Check these possible problems: v Ensure that the FTP or TFTP server is running. v Ensure that a firewall is not blocking access to the FTP or TFTP server. v Ensure that correct access permissions are set on files and directories on the FTP or TFTP server. v Ensure that the BladeCenter Settings tab (Release Management > Updates > Settings > BladeCenter) is configured with the correct settings to access and use the FTP or TFTP server. Check that the following settings are correct:
215
Network Interface field shows the correct FTP/TFTP server IP address TFTP root directory or FTP user home directory path. These directories must already exist on the TFTP or FTP server. FTP user name and password v In many cases, the update has to be installed using a specific protocol (FTP or TFTP). Ensure that the correct protocol is configured. Note that if the update descriptor indicates that both FTP and TFTP are supported, and if both FTP and TFTP servers are configured on the BladeCenter Settings page, the TFTP server will be used. v Ensure that the system selected to be used as the FTP or TFTP server has been unlocked and is online. v Ensure that the target device has been unlocked and has an active connection. v Ensure that sufficient disk space is available on the configured FTP or TFTP server.
Installing out-of-band updates for IBM BladeCenter devices using SNMP fails
This problem can occur when using SNMP for the installation of IBM BladeCenter updates.
Problem
Installation failures occur when attempting to install updates for IBM BladeCenter devices (such as IBM BladeCenter Management Modules, Advanced Management Modules, and Pass Thru Modules) using SNMP.
Resolution
For installation staging task failures, see IBM BladeCenter Install and Installation Staging tasks fail when using an FTP or TFTP server. Also check these possible (SNMP) install task problems: v Ensure that access has been granted to the Management Module installed in the IBM BladeCenter. v Verify that you have network connectivity to the Management Module in the IBM BladeCenter. v Ensure that you selected and configured the necessary settings to use a TFTP server in the BladeCenter Settings tab (Release Management > Updates > Settings > BladeCenter). Updates installed using SNMP need to be obtained from a TFTP server. v If using an external TFTP server, ensure that it is unlocked (access granted) and online. v When using a different TFTP server than the one included with the management server, make sure you correctly set the TFTP root directory. If that value is not set appropriately, the updates will not be accessible by the Management Module using TFTP, which will cause the installation process to fail. The TFTP root directory must already exist on the TFTP server. v When using a different TFTP server than the one included with the management server, make sure the Relative path to updates value is not too long. A long path name can cause the installation process to fail. A path name shorter than 25 characters in length is recommended. v For successful installations, consider these points:
216
SNMP agents must be enabled in the IBM BladeCenter Management Module. Otherwise, communication is not possible. You can enable this using IBM Systems Director by creating a Management Module Network SNMP Configuration template, and applying it to the IBM BladeCenter Management Module. When creating the Management Module Network SNMP Configuration template, the IBM BladeCenter Management Module must be configured to have the SNMP Access Type with a value of SET, for the installation process to succeed. Alternatively, you can use the Web-based interface for Advanced Management Module or Management Module, under SMPv3 User Profile, to change the Access Type to SET. SNMP Version 3 communication requires authentication (or credentials) as it is more secure. When creating the Management Module Network SNMP Configuration template, select SNMP Version 3, and fill in the appropriate authentication settings. SNMP Version 3 credentials can also be obtained from the IBM BladeCenter Management Module, if possible, when it is being unlocked. This normally means that the privacy protocol is set to NONE for the User ID used to unlock the IBM BladeCenter Management Module. SNMP credentials in the Management Module Network SNMP Configuration template used by IBM Systems Director must match the SNMP credentials in the IBM BladeCenter Management Module itself. Check these credentials.
Installing out-of-band updates for IBM BladeCenter devices using Telnet fails
This problem can occur when using Telnet for the installation of IBM BladeCenter updates
Problem
Installation failures occur when attempting to install updates for IBM BladeCenter devices (such as switch and bridge modules) using Telnet.
Resolution
For installation staging task failures, see IBM BladeCenter Install and Installation Staging tasks fail when using an FTP or TFTP server. Also check these possible (Telnet) install task problems: v Ensure that access has been granted to the target switch module in the IBM BladeCenter. v Verify that you have network connectivity to the target switch module in the IBM BladeCenter. v Ensure that you selected and configured the necessary settings to use the appropriate FTP or TFTP server in the BladeCenter Settings tab (Release Management > Updates > Settings > BladeCenter). Some switches use FTP only; some use TFTP only; some can use either FTP or TFTP. If the update descriptor specifies that both FTP and TFTP are supported, and both FTP and TFTP servers are configured on the BladeCenter Settings tab, then TFTP will be used. v Ensure that the FTP or TFTP server is unlocked (access granted) and online. v When using an FTP server or an external (other than the management server) TFTP server, make sure you correctly set the FTP user root directory or the TFTP root directory. If that value is not set appropriately, the updates will not be
217
accessible by the target switch module using FTP or TFTP, which will cause the installation process to fail. The directory must already exist on the FTP or TFTP server. v When using an FTP server or a TFTP server other than the management server, make sure that the Relative path to updates value is correct. v The FTP user name and password must be correct. Note that IBM Systems Director 6.1 supports the Anonymous FTP function (user name is 'anonymous'). However, for Anonymous FTP transfers to work, the FTP server must support (and enable) Anonymous FTP, and the Anonymous FTP password must conform to the requirements of the FTP server.
Install fails for IBM BladeCenter switch module updates that support both TFTP and FTP protocol, when only an FTP server is configured
This problem occurs when using FTP to install an IBM BladeCenter update that supports both TFTP and FTP protocol. This problem occurs even if the BladeCenter Settings tab correctly indicates that TFTP is not to be used, and the FTP server information is correct.
Problem
The IBM BladeCenter switch module update supports TFTP and FTP. This is known from the update's metadata files - readme, change history, or descriptor (XML) files. Only an FTP server is available, and it has been configured in the BladeCenter Settings tab correctly. No TFTP server is configured. The Installation Staging task or the Install task for those IBM BladeCenter switch module updates fails.
Explanation
By default, updates that support both TFTP and FTP will be staged and installed using TFTP. This is determined at the time that the update is downloaded or imported. Therefore, in the default case, the Installation Staging task and Install task for those updates will still try to use TFTP. Since there is no TFTP server configured, those tasks fail.
Resolution
There are two alternatives here: 1. Configure a TFTP server using the BladeCenter Settings tab. The Installation Staging task and the Install task will then be able to use TFTP to that server, and they should work successfully. 2. Re-configure IBM Systems Director to use FTP in cases where the update supports both TFTP and FTP. To do this, perform the following steps: a. Edit the UpdateManager_x_bc.properties file, named:
Director_Install_Directory/data/UpdateManager_x_bc.properties
where Director_Install_Directory is the directory where IBM Systems Director is installed: b. Change the DEFAULT_XFER_PROTOCOL property from 1 (for TFTP) to 2 (for FTP). c. Save the file.
218
d. Remove the applicable updates. This can be done from a command window using this command:
smcli cleanupd m update_name
This step is optional if the updates are going to be imported back into IBM Systems Director. This step is needed if the updates are going to be downloaded from the provider of the update. e. Download or import the updates again. If you are using the smcli importupd command and the updates were not previously deleted, the -o (or --overwrite) option should be used.
Note that the DEFAULT_XFER_PROTOCOL property affects only updates that support multiple protocols for installation staging and install tasks. Updates that support only TFTP will still need a TFTP server, and updates that support only FTP will still need an FTP server.
Installing an update takes too much time

The install of updates is slow.
Problem
When installing updates, the process is slower than expected.
Investigation
These are steps that can be performed during the install of an update. Step 3 is always performed. Steps 1 and 2 are done as part of the installation process, if it is determined that they have not already been done separately. 1. Download update over the Internet to the management server. 2. Stage the update for installation over the customer network. 3. Install the update using an installer on the system. Each of these steps can be run individually to determine which step is taking the most time to complete. The size of the update will greatly impact the performance of the first two steps. Before installing the update, the download task can be selected to download the update. Once this task completes, the installation staging task can then be ran on the update to stage it over the customer network for eventual installation. If manually running the download and install staging tasks does not improve the time that it takes to run the install task, compare the performance of installing with IBM Systems Director to installing the update using the native platform methods. The time should not be significantly different. If the time is significantly different, ensure that network connectivity and response is good, and check the logs for errors. Remember that some updates take a considerable amount of time to install due to the nature of the platform, operating system, or the update itself.
219
Resolution
Run the installation staging task before the install maintenance window, to avoid the time it takes to download and transfer the update over the network. The install task should then provide better performance during the installation maintenance window.
Manually installed updates are not displayed as installed

An update that was manually installed does not show as having been installed.
Problem
After installing an update manually outside of update manager, the update still shows as needed by the system.
Investigation
When installing an update manually, verify that the installation finishes successfully, that any necessary system restarts are performed, and that the system is unlocked and its inventory is current.
Resolution
This happens because update manager automatically runs inventory collection after installing an update. Since the update was manually installed, inventory collection must also be performed manually. Ensure that the system is unlocked and that the collected software inventory is current.
Manually uninstalled updates are displayed as still being installed

An update that was manually uninstalled still shows as being installed.
Problem
After uninstalling an update manually outside of update manager, the update still shows as installed on the system.
Investigation
When uninstalling an update manually, verify that the uninstall finishes successfully, that any necessary system restarts are performed, and that the system is unlocked and its inventory is current.
Resolution
This happens because update manager automatically runs inventory collection after uninstalling an update. Since the update was manually uninstalled, inventory collection must also be performed manually. Ensure that the system is unlocked and that the collected software inventory is current.
Install fails when using system groups or update groups

Performing an install or uninstall fails when using one or more system groups or update groups.
220
Problem
The Install or Uninstall task using system groups or update groups does not succeed due to missing update requirements or dependencies.
Explanation
The Install wizard and Uninstall wizards do not resolve group membership until their tasks runs. Group membership is not resolved at the time that the wizard is run. This means that the task may fail because information about updates, such as: update requirements, manual downloads, manual installation, and system restarts cannot be determined at the time that the Install or Uninstall wizard is run.
Resolution
While using the Install or Uninstall wizard, select each update to be installed individually instead of selecting the update group. This will cause the wizard to obtain the necessary information about update requirements.
Updates from an update group have not been installed

When installing an update group, some members are installed and others are not.
Problem
You schedule the installation of an update group for one or more systems. When the task completes, you find that some of the updates that were in the group when the task was scheduled, have not been installed.
Investigation
There are several possible causes: v The update group membership changed between the time that the task was scheduled and when it ran. If an update is removed from the group after the task was scheduled but before it ran, this update will not be installed. Keep in mind that the membership of an update group is not resolved when the update task is scheduled. It is resolved when the task runs. v The update group contained updates that require a manual download. A manual download cannot be automatically performed, so that task fails. Since the membership of the update group was not determined when the update task was scheduled, the user could not be alerted to this possibility. v The update group contained updates that had special install instructions. Similar to the previous scenario, this cannot be done automatically, and the user cannot be alerted to this possibility in advance.
Resolution
Consult the task log to determine which of the listed possible causes has occurred. Another solution is to run through the install wizard and select these updates that have failed, instead of using an update group. The wizard can detect manual downloads and special installation instructions when it is given only one update to install.
221
Scheduled Install or installation staging task fails with a connection error

This problem affects the install and installation staging tasks when working with remotely accessed systems.
Identifier
ATKUPD921E: An error occurred while attempting to connect the system system name using the Remote Session Service.
Problem
If the connection to the remote system is lost between the time that the task is scheduled, and the time that the task runs, the scheduled task will fail with a connection error.
Investigation
To determine if the noninteractive task failed for this reason, examine the task history log. 1. From the IBM Systems Director Web interface, click Task Management > Active and Scheduled Jobs. 2. Click on the failed task. 3. 4. 5. 6. Click the Logs tab. Right click on the failed activation. Click Show Logs. Examine the logs for the connection error, ATKUPD921E or similar messages.
Explanation
The Install and Installation Staging Wizards will check that a system is unlocked and accessible. However if the task is scheduled to run in the future, the communication with the remote system could be lost before the task runs.
Resolution
Check the remote system and ensure that it is unlocked and accessible from the network.
Path length is limited to 64 characters when updating IBM BladeCenter Out of Band components
This limitation affects update manager when applied to out-of-band IBM BladeCenter components, such as Management Modules, Advanced Management Modules, and Pass-through Modules.
Problem
The install task for an out-of-band IBM BladeCenter update will fail when the path of the update on the TFTP staging server has a length greater than 64 characters. This is a limitation of updates to IBM BladeCenter Management Modules, Advanced Management Modules, and Pass-through Modules.
222
Resolution
Ensure that path of the TFTP staging server is fewer than 64 characters in length.
If you are updating IBM BladeCenter Management Modules with version BRET86C or earlier, the path length is limited to 32 characters.
Staging of updates to TFTP server can fail on extremely slow networks

This limitation affects update manager when staging updates to a TFTP server.
Problem
On extremely slow networks, staging of updates to TFTP server may exceed an internal timeout value, causing the install task to report a failure, even though the file transfer and install process might complete some time in the future.
Resolution
It is suggested that you move that TFTP staging server or choose a different TFTP staging server. Select one whose network connection speed is faster.
Custom criteria chooser shows incorrect or missing update types for the Version category of IBM Systems Director
This problem affects all IBM Systems Director agent systems.
Problem
This problem can occur when viewing the custom criteria chooser for selected systems (for example, during a Check for updates task, or when creating an Update group). The Version update types that are displayed for the IBM Systems Director updates (for example, 5.20, and 6.1) are missing or incorrect with respect to the selected systems. An example is if the selected system has a IBM Director 5.20 agent installed on it, no update types are shown. The correct value of 5.20 should be displayed.
Explanation
This occurs when information describing the properties of an OperatingSystem resource has not been collected properly during a System Discovery task. Specifically, it is related to the ManagementSoftware property of the OperatingSystem not being discovered correctly.
Resolution
Here are some specific steps to follow to ensure that discovery works correctly: 1. From Navigate Resources, select All Systems and locate the system. There should be a row representing the OperatingSystem resource for the system. If this is not found, then System Discovery did not work or was not yet performed.
223
2. The OperatingSystem resource should have OK in the Access column. If not, the system might need to be unlocked. 3. Once the OperatingSystem resource is unlocked, a Server resource should also exist for the system, and it should have OK in the Access column. 4. Once the Server and OperatingSystem resources both appear as unlocked, viewing the properties of the OperatingSystem should show the version of the IBM Systems Director agent on the system (if any) in the Management Software property. The Version update type values that are shown in the custom criteria chooser of update manager will reflect the value of this property. Update manager will not work correctly if the property was not populated with the correct value during System Discovery. 5. If the Management Software property was not discovered correctly, see the troubleshooting information for System Discovery. As an example, it might be necessary to disable the SLP service on the selected system and then restart the IBM Systems Director services in the correct order.
The Management Software property is populated at different times, according to the agent type. v For IBM Systems Director Platform Agent managed systems - during System Discovery v For IBM Systems Director Common Agent managed systems - when the OperatingSystem resource for the system is unlocked. Information about the Management Software version might not be refreshed in certain situations when an agent is upgraded to a newer version. A refresh can be forced by doing a System Discovery for the system after it has been upgraded.
Updating IBM Director Agent version 5.20.1 on operating systems other than Microsoft Windows fails
Updating IBM Director Agent version 5.20.1 on operating systems other than Microsoft Windows fails
Problem
When using an operating system other than Microsoft Windows, updating IBM Director Agent version 5.20.1 fails. The status of the install request will be "Complete with errors". The task log will contain entries similar to this sequence of errors
########################################################################### ATKUPD702I Update Installation service: A new request is active. ATKUPD740I Update Installation service: Provider "Legacy Agent Install Extension" is active. ATKUPD760I Start processing update "IBMDirectorAgent.xLinux.5.20.2.DR522AGTXL" and system "name_of_system". DNZSWD204W Error installing update: "IBMDirectorAgent.xLinux.5.20.2.DR522AGTXL" DNZSWD205I Due to errors on the agent, the upgrade must be applied manually. Install the following package on the target system: "C:/Program Files/IBM/Director/data/updateslib/Director/IBMDirectorAgent.xLinux. 5.20.2.DR522AGTXL/dir5.20.2_agent_linux.sh" ATKUPD734E One or more errors were encountered during the "UpdateInstallTask" task. See task log for details. ATKUPD726E The update install task has finished with errors.
224
The presence of errors DNZSWD204W and DNZSWD205I is most significant.
Resolution
You must manually update IBM Director Agent version 5.20.1 on operating systems other than Microsoft Windows.
To update IBM Director Agent version 5.20.1 manually, complete the following steps: 1. Locate the name of the installable that must be installed on the agent. It is in the text of the DNZSWD205I message. 2. Locate this file on the management server. 3. Manually install this file on the agent.
AIX upgrades that skip a Technology Level may not report correct new level
This problem affects upgrading AIX systems to a new Technology Level (TL).
Problem
When attempting to upgrade an AIX system to a new TL, if the upgrade skips a TL, the resulting installation may not report that the AIX system is at the new, expected level. An example is that an attempt to upgrade from AIX 5300-06-08-0831 to AIX 5300-08-03-0831 is an upgrade from AIX 5.3 TL6 SP8 to AIX 5.3 TL8 SP3, skipping AIX 5.3 TL7.
Explanation
New AIX base level filesets may be introduced in a Technology Level. For example, when upgrading from AIX TL6 to AIX TL8, there might be new base level filesets that were introduced in AIX TL7. Updates to these base level filesets (for example, updates that must be installed in order for a system to report that it is at AIX TL8) might not have been selected for installation, because an upgrade operation can only select updates for previously installed filesets (for example, those previously installed on AIX TL6). After the upgrade is completed this results in the AIX system not reporting that it is at the expected Technology Level.
Resolution
After an upgrade is completed that results in the AIX system not reporting that it is at the expected Technology Level, the installation should be performed again. This could result in the installation of the missing filesets that are necessary for the AIX system to report the correct operating system level. If no change occurs after performing the installation again, contact your service provider to determine the missing filesets that must be installed in order for the AIX system to report the expected level.
Best practices for working with updates for IBM i

This problem affects users who are installing updates to IBM i.
225
Problem
Update groups for IBM i agents can contain a large number of updates, which might cause performance, memory and file space issues on the IBM Systems Director Server.
Actions
1. Use a 64bit system with IBM Systems Director Server installed. 2. Make sure that input/output adapters are properly configured for IBM i. Input/output adapters should not show a degraded status. In some configurations, two input/output adapters have to be physically paired. Refer to the IBM i documentation for more information. 3. For tasks that contain a large number of updates, such as IBM i PTF groups, it is recommended you use a high performance database, such as DB2. 4. When working with IBM i updates, it is recommended that you work with one update group at a time. For example, when checking for IBM i 5.4 updates, first check for Hiper PTFs and let that check complete before checking for additional updates. Performing three individual checks will provide better results then attempting a single check for Hiper, DB2 and Java, for example. In addition, to optimize checks, you can schedule your update task checks. Finally, it is a good practice to run tasks that check for and install updates during non-peak hours. 5. Avoid selecting updates that are not necessary for your system. Storing unnecessary updates on the IBM Systems Director Server affects performance. 6. To reduce the time needed to install IBM i updates, the updates that are needed for install can be downloaded from the fix service provider to the IBM Systems Director Server, before the install task is started. When the updates are already on the server, the install only needs to send the updates from the IBM Systems Director Server to the IBM i system. The install task can be scheduled to avoid peak hours. 7. The performance of the IBM Systems Director Server running on an AIX , Linux on Power Systems, or Linux for System x operating system can be improved by increasing the amount of memory available to Java. To increase the memory, edit <Director install directory> /lwi/conf/overrides/ director.javaopt. On 32bit systems that have IBM Systems Director Server installed, change the value for -Xmx to 1792m. For example, -Xmx1792m. Important: Before increasing the memory available to Java, make sure there is enough physical memory for the increased size. 8. When using the IBM Systems Director Server running on AIX or Linux, the /opt filespace is used to store the updates including the savf files for IBM i updates. It migh be necessary to increase the size of the /opt filesystem. 9. To allow more time for collecting inventory on an IBM i system, the default discovery timeout value on the IBM Systems Director Server can be increased by editing a properties file that is read when the IBM Systems Director Server is started. The timeout value is set by adding or changing the following property in the lwi/conf/overrides/USMiKernel.properties file:
perf.extended.discovery.timeout=nn
where nn is the number of minutes before a timeout occurs. The suggested value is 75 minutes. 10. When running a check for an updates or collect inventory task, another job is submitted in the background after the task completes. It is important to allow
226
sufficient time for the background job to complete before starting an install updates task. This background job, named Update Compliance, can be monitored from the Applied Activities tab on the System Properties page. 11. The performance of the IBM Systems Director Server can be increased by removing updates that are not needed. For example, if WebSphere group PTFs have been downloaded but are no longer applicable to the systems because the product has been removed, then those updates can be removed from the IBM Systems Director Server. To remove updates from the server, use this command:
smcli cleanupd am
Uninstall fails because a restart of an IBM i system is required

This problem affects IBM i (formerly i5/OS) systems.
Problem
When you try to uninstall updates to IBM i systems using update manager, the task will fail if some of the PTFs require a restart to be done. The message 'DNZPI5080E The uninstall failed because the system requires a restart to complete the uninstall' is in the log file. IBM i systems are not restarted automatically by update manager.
Resolution
Perform the restart.
Show installed updates and Show needed updates tasks do not display all updates
The show updates views do not display all updates. Some updates are missing.
Problem
When using Show installed updates, Show needed updates, viewing update groups, or other places where updates are listed, not all updates are displayed.
Investigation
Ensure that the system is unlocked and the collected software inventory is complete and current. Once inventory completes, it needs to be processed, which can take several minutes. When complete, the update information on what is needed or current should be accurate.
Explanation
Update manager will include in these views only the updates that update manager supports. Therefore, Show installed updates should not be considered a complete view of all updates installed on a system, but only a view of the updates supported for management by update manager. This rule applies to all views. Likewise, updates that cannot be managed due to inadequate information might not be displayed. If an update is installed but information on that update has yet to be acquired by a Check for updates, the update will not be visible for management.
227
Updates that are part of a collection, such as a service pack or larger update package, will not be individually displayed unless the Related resources action is chosen on the parent update collection.
Resolution
If an update is supported by update manager and is not being displayed, ensure that information on the update has been downloaded by running the Check for updates task. Also, ensure that the collected software inventory for the system is current and complete.
Virtualization manager troubleshooting

This section provides information about problems and workarounds for the virtualization manager plug-in.
Virtualization environment troubleshooting

These problems can occur when you use IBM Systems Director virtualization manager in any supported virtualization environment.
No event is sent to event log

This problem can affect VMware VirtualCenter or VMware ESX Server systems that have IBM Director Agent version 5.20.x installed, along with IBM Systems Director Virtualization Manager Agent, version 1.2.x
Problem
You select to run a task on a system in a VMware VirtualCenter or VMware ESX Server environment, for example, create farm, add or remove host, create virtual server, delete virtual server, relocate virtual server, or virtual server power operations. However, the event log does not contain information about the success or failure of the task.
Explanation
This situation can occur when the agent has been discovered by multiple instances of IBM Systems Director Server. It is recommended that you discover the VMware VirtualCenter or VMware ESX Server system from only one instance of IBM Systems Director Server.
Resolution
When the agent is running on Windows, you can resolve the problem of the systems being discovered by multiple instances of IBM Systems Director Server by removing extraneous server references from the agent repository. Complete the following steps: 1. On the system where the agent is installed, use the twglstsr tool to get a list of all management servers where the agent is discovered and unlocked. Each entry in the output of twglstsr includes the UID of the agent on the corresponding management server. 2. To remove extraneous management server reference from agent repositories, run the following command:
twglstsr /REMOVE:UID
228
where UID is the user ID of the agent on the management server that you want to remove. On Windows the server reference is maintained in netdrvr.ini When the agent is running on Linux, you can verify that the problem of the system being discovered by multiple instances of IBM Systems Director Server exists by checking the srvreg.ini file in the data directory.
Event filters that use extended details to monitor the creation of a virtual server
This problem can affect any virtualization manager subagent.
Problem
Event filters that use extended details to monitor the creation of a virtual server with a specific name are ignored.
Resolution
Event filters for virtual servers that use extended details must designate the virtual server ID and not the virtual server name in the Values (String) field. Since a virtual server ID is not assigned until after the creation of a virtual server, you cannot create an event filter to monitor the creation of virtual servers.
Virtual servers disappear after relocation

This problem only affects virtualization manager subagents for VMware ESX Server and Microsoft Virtual Server.
Problem
A virtual server that is being statically relocated can become inaccessible when network connectivity is lost to any of the involved systems. This could be the source host, destination host, or IBM Systems Director Server that is managing the hosts involved in the relocation.
Resolution
When this situation happens, the virtual server stays in a transition state on the source host, but is not accessible. The recovery steps differ based on the virtualization manager subagent that you are using. (Virtualization manager subagent for Microsoft Virtual Server only) Further, all the virtual servers that are on the same partition as the virtual server that was being relocated are also inaccessible. These virtual servers are not destroyed but are not visible to virtualization manager or to the host system. The files that define the virtual servers are still available on the source or destination host depending on what phase of relocation was occurring when the network failure occurred. The affected virtual servers must be recovered following a manual procedure. Virtualization manager subagent for VMware ESX Server: Complete some or all of the following steps to manually recover the virtual servers on an VMware ESX Server host that are affected by this problem. In some cases, not all steps are needed. As soon as the affected virtual servers are accessible again, you can stop completing the steps. 1. From the IBM Systems Director Web interface, delete the affected virtual server.
229
2. From the source host system, collect inventory to ensure its virtual servers are discovered. If the affected virtual servers are still not accessible, proceed to the next step. 3. From the destination host system, collect inventory to ensure its virtual servers are discovered. If the affected virtual servers are still not accessible, proceed to the next step. 4. Find the configuration file of the virtual server that was being relocated when the network connectivity was lost. Most likely, the configuration file is on the source host, but it could be on the destination host. The configuration file location varies by the version of ESX you have installed. The configuration file usually has a .vmx extension. See the following table to determine the configuration file location for the version of ESX that you have installed.
ESX version ESX 2.x ESX 3.x Configuration file location /home/vmware or /root/vmware /vmfs/volumes/vmfs_volume_name/vm_name
5. After you have the full path to the configuration file of the virtual server, register the virtual server with the host that contained the file. To do so, you can register the virtual server using the VMware management software or client. Virtualization manager subagent for Microsoft Virtual Server: Complete the following steps to manually recover the virtual servers affected by this problem on Microsoft Virtual Server hosts: 1. From the IBM Systems Director Web interface, delete the affected virtual server. 2. From the source host system, find the unmounted partition that the virtual server was using. 3. From the source host system, mount the partition. 4. From the mounted partition, find the configuration file of the virtual server that was being relocated when the network connectivity was lost. 5. From the source host system, register the virtual server with the source host. 6. From the source host system in the IBM Systems Director Web interface, collect inventory to ensure its virtual servers are discovered.
Subagent for VirtualCenter takes precedence over subagent for ESX

Problem
Virtual servers that are associated with a host that contains virtualization manager subagent for VMware ESX Server are deleted when the associated host is removed from a virtual farm in VMware VirtualCenter.
Resolution
Make sure that you understand that virtualization manager subagent for VMware ESX Server is not for use with hosts that are being managed with VMware VirtualCenter. However, if this scenario should occur, be aware that the virtualization manager subagent for VMware VirtualCenter always takes precedence over the virtualization manager subagent for VMware ESX Server.
230
This symptom can occur when a host is being managed with VMware VirtualCenter and it is also running virtualization manager subagent for VMware ESX Server, which is not a supported configuration. Further, the host was added to a virtual farm in VMware VirtualCenter, but is later removed from the virtual farm, which in turn deletes all associated virtual servers. Although you can rediscover the virtual servers that are associated with the host that is running virtualization manager subagent for ESX, this action causes all event action plans that contain references to the deleted virtual servers to become invalid. This happens because the rediscovered virtual servers have different object IDs than the virtual servers that were deleted.
CPU utilization is not reported for hosts running VMware ESX Server 3.0 or 3.0.1 that are being managed by VMware VirtualCenter 2.0 or 2.0.1
This problem affects hosts running VMware ESX Server 3.0 or 3.0.1 that are being managed by VMware VirtualCenter 2.0 or 2.0.1.
Problem
When you try to view CPU utilization in IBM Systems Director for hosts running VMware ESX Server 3.0 or 3.0.1 that are being managed by VMware VirtualCenter 2.0 or 2.0.1, the CPU utilization attribute does not appear on the host object. This problem occurs because CPU utilization is currently not reported for hosts running VMware ESX Server 3.0 or 3.0.1 that are being managed by VMware VirtualCenter 2.0 or 2.0.1.
Resolution
Currently, this is a limitation for hosts running VMware ESX Server 3.0 or 3.0.1 that are being managed by VMware VirtualCenter 2.0. However, to enable reporting for CPU utilization through virtualization manager for hosts that are being managed by VMware VirtualCenter 2.0.1, you can edit the vpxd.cfg file on the host system. To edit the vpxd.cfg file, complete the following steps: 1. Locate the vpxd.cfg file. The vpxd.cfg file is typically located in the following directory: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter 2. Add the following lines to the vpxd.cfg file:
<vpxd> <stats> <filterLevel>4</filterLevel> </stats> </vpxd>
3. Ensure that the perfRefreshEnabled property is set to true. For example, change the following line:
<perfRefreshEnabled>false</perfRefreshEnabled>
to the following:
<perfRefreshEnabled>true</perfRefreshEnabled>
231
Network connectivity is lost

This problem can occur when you use IBM Systems Director in any supported virtualization environment.
Problem
Network connectivity is lost to resources being managed by IBM Systems Director.
Resolution
After network connectivity is restored, you can complete the following tasks to check for any residual problems. 1. If any managed resources appear to be missing, you can attempt to discover and collect inventory on them. 2. Check for any error states on managed resources, and refer to any information associated with the error. 3. If necessary, you can attempt to restart Common Agent on a managed resource by running the endpoint stop and endpoint start commands on your agent system. 4. If the network connectivity loss occurs during a virtual server relocation, refer to Virtual servers disappear after relocation for more information.
Static virtual server relocation does not complete when guest operating system is locked
Problem
If a turned-on virtual server is relocated, but the guest operating system is locked, the relocation process cannot be completed as the virtualization manager subagent for Microsoft Virtual Server cannot turn off the virtual server. Turning off the virtual server is required for static relocation.
Resolution
Use the Administration Web site for Microsoft Virtual Server to manually turn off the virtual server. If the virtual server is turned off within the timeout period of the virtualization manager server (generally 5 minutes), virtualization manager detects the state change of the virtual server and continues the relocation.
Relocation plan fails when activated

This problem can occur in any supported virtualization environment.
Problem
When you activate a relocation plan, it fails unexpectedly.
Explanation
IBM Systems Director does not perform any validation steps before running a relocation plan. The administrator who activates the relocation plan must ensure that the relocation plan is accurate for the current environment. If resources that are defined in the relocation plan have changed, or the plan has been activated previously, it might not be valid.
232
Resolution
If necessary, edit the relocation plan to be accurate for the current environment. Then try activating the relocation plan again.
Virtual server cannot be registered on destination host

This problem affects systems using virtualization manager subagent for Microsoft Virtual Server.
Problem
When unregistering a virtual server, Microsoft Virtual Server sometimes leaves a link file (.lnk) on its associated host. This link file prevents the virtual server from being registered on the destination host. This problem is exposed during relocation as the relocation process involves unregistering and reregistering a virtual server.
Resolution
Delete the link file that is associated with the virtual server from the source host. The event log from Microsoft Virtual Server lists the name of the link file. After the file is deleted, manually register the virtual server to the destination host.
Virtual server does not shut down or turn off when guest operating system is locked
Problem
If you use IBM Systems Director to shut down and turn off a virtual server when the guest operating system is locked, the virtual server is not shut down or turned off. Further, in IBM Systems Director, the virtual server remains in the transition state.
Resolution
You must use the Administration Web site for Microsoft Virtual Server to turn off the virtual server. After the virtual server has been turned off through the Administration Web site, use IBM Systems Director to rediscover the virtual server so that IBM Systems Director reflects the turned-off state.
Virtual server does not turn on

Problem
Sometimes unregistering a suspended virtual server in a Microsoft Virtual Server environment can cause the files for the virtual server to become corrupted. The problem becomes evident when the virtual server is reregistered later. The virtual server can be reregistered, but it will not turn on as expected.
Resolution
If you plan to use a virtual server again, be sure that it is not suspended before you unregister it.
233
Virtual server object disappears from IBM Systems Director and Deleted event occurs
This problem affects systems using virtualization manager subagent for VMware ESX Server.
Problem
If you turn off a virtual server with the VMware Console and select to always create a new universal unique identifier (UUID) and later use IBM Systems Director to relocate that virtual server, the UUID for the virtual server is changed when the virtual server is eventually turned on at the destination host. This sequence of events causes the virtual server object to be deleted from IBM Systems Director and causes a virtual server, Deleted event to occur.
Resolution
To restore the virtual server object to IBM Systems Director, you must rediscover the virtual servers on the host.
Unable to specify 128 MB of memory for virtual server

This problem affects virtual servers in the Microsoft Virtual Server environment.
Problem
When using the Create Virtual Server or Edit Virtual Server tasks on a virtual server that is managed by Microsoft Virtual Server, you are unable to specify 128 MB of memory for the virtual server.
Explanation
Although Microsoft Virtual Server supports virtual servers with 128 MB of memory, IBM Systems Director requires a minimum of 256 MB of memory for a virtual server in the Microsoft Virtual Server environment.
Virtual server state change not reflected in IBM Systems Director

This problem affects virtualization manager subagent for Microsoft Virtual Server.
Problem
You use the Discard from saved state task in the Microsoft Virtual Server console to change the state of a virtual server. For example, the Discard from saved state task changes a virtual server from a suspended state to an offline state. However, the new state is not reflected accurately in IBM Systems Director.
Explanation
The Microsoft Virtual Server software development kit does not provide a notification for virtual server state changes related to the Discard from saved state task; therefore, IBM Systems Director is unable to receive the notification and update the virtual server state.
Resolution
In IBM Systems Director, collect inventory for the host that contains the virtual server that is displaying an incorrect state.
234
Virtualization manager tasks fail on new virtual server

This problem affects stand-alone systems running VMware ESX Server.
Problem
When you attempt to run a virtualization manager task, such as Power On, on a new virtual server, the task completes with errors.
Explanation
The VMware SDK is returning the incorrect Universal Unique Identifier for the newly created virtual server.
Resolution
Perform the collect inventory task on the VMware ESX Server host, and retry the virtualization manager task on the virtual server.
Migrating status does not reset when relocation fails

This problem can occur in any supported virtualization environment.
Problem
When you start a virtual server relocation that cannot be completed successfully, the status of that virtual server changes to Migrating, and is unable to recover to its previous status after the relocation fails.
Resolution
After the relocation fails, perform the collect inventory task on the virtual server, and the virtual server should return to the correct status.
DNS fields are blank for initial network configuration on ESX

This problem can affect VMware ESX Server managed systems with the Platform Agent installed.
Problem
When you perform DNS network configuration on ESX with Platform Agent installed, the DNS server and DNS domain suffix values are blank.
Explanation
This issue is observed on a freshly installed ESX operating system and while applying network configuration for the first time only.
Resolution
Repeat the same procedure to apply the DNS configuration again, and the issue will not be observed.
Incorrect power state displayed for Hyper-V virtual servers

This problem affects the Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 virtual servers, when power operations are performed on the virtual servers by using the vendor software rather than by using IBM Systems Director.
235
Problem
You perform a power operation, such as Power On or Power off, on your Hyper-V virtual server by using your vendor software. You notice that the power state for the virtual server is not accurately displayed in the IBM Systems Director Web interface.
Resolution
To immediately refresh the IBM Systems Director Web interface to accurately reflect the power state of your virtual server, you can perform one of the following manual steps: v Collect inventory on the managed host system. v Right-click the managed host system, click Security > Verify Connection and select Query vital properties. Alternatively, you can adjust the frequency for collecting inventory on the operating system. Expand Settings > Server Preferences. For the Operating System resource type, change the Query Vital Properties Interval to the smallest frequency interval.
Power Systems environment troubleshooting

These problems can occur when you use IBM Systems Director virtualization manager in an IBM Power Systems environment.
Virtual server devices are missing

This problem can affect virtual servers that are managed by Hardware Management Console or Integrated Virtualization Manager.
Problem
The virtual disks, physical volumes, or devices that you expect to see do not appear in edit virtual server, create virtual server, or edit host tasks. In addition, the virtual disks, physical volumes, or devices do not appear in the virtualization topology perspectives views. You might also be receiving the following error: The operation cannot be performed because the system or one or more of its associated resources, has not been discovered, or it has been discovered but subsequently removed.
Explanation
You might be using an unsupported version of Hardware Management Console or Integrated Virtualization Manager, or the system inventory might not be current. Another possibility is that the Virtual I/O Server that manages the virtual servers might not be powered on. The Virtual I/O Server must be powered on for the additional devices and resources to be visible to IBM Systems Director.
Resolution
To attempt to resolve the problem of devices not appearing in IBM Systems Director, complete the following steps:
236
1. Navigate to the Virtual Servers and Hosts view. From the navigation pane of IBM Systems Director, click Navigate Resources > Virtualization Groups > Virtual Servers and Hosts. 2. Check for systems with one of the following problem listed in the Problems column: v HMC version is not supported v IVM version is not supported v HMC version is unknown v HMC version is unknown v The Virtual I/O Service is not available 3. If you see a problem for a platform manager version being unsupported, check the supported virtualization software topic to find a list of platform managers that are supported. 4. If a Virtual I/O Server is listed with the problem, Virtual I/O Service is not available, you might need to power it on to discover the devices it manages. If the power on action is appropriate for the Virtual I/O Server, select the Virtual I/O Server, click the Actions menu and select Power and Energy > Power on. The virtual disks, physical volumes, and devices are automatically discovered after IBM Systems Director receives the power on event. 5. If for some reason the devices do not appear in the virtualization topology perspectives after ensuring that your platform manager version is supported, and if necessary, powering on the Virtual I/O Server, perform the collect inventory task on the host. From the navigation pane of IBM Systems Director, click Inventory > View and Collect Inventory. After submitting the Collect Inventory request, wait several minutes for the data to refresh, and check the virtualization topology perspective again.
Version of HMC or IVM is unsupported

This problem can affect systems that are managed by Hardware Management Console or Integrated Virtualization Manager.
Problem
You might be receiving the following error: The operation cannot be performed because the version of the HMC or IVM is not supported.
Resolution
To resolve the problem of an unsupported platform manager, complete the following steps: 1. To check the version of Hardware Management Console or Integrated Virtualization Manager that is running on the platform manager, right-click the platform manager and select Properties. 2. Ensure the version of Hardware Management Console or Integrated Virtualization Manager that is running on the platform manager is supported. Check the Virtualization software supported topic for more information. 3. If necessary, update the Hardware Management Console or Integrated Virtualization Manager to a supported version.
Virtualization service cannot be found

237
Problem
All systems managed by the HMC or IVM are displaying a critical error status. The message associated with the critical error is, Virtualization service cannot be found. Each virtual server and host associated with the HMC or IVM also shows an error, The resource cannot be reached.
Explanation
Secure Shell (SSH) might not be properly enabled for remote command execution on the platform manager.
Resolution
To attempt to resolve the problem of virtualization service not being found, ensure you have enabled the platform manager for remote command execution by starting the SSH service. See the following topics for more information: v Enabling the HMC for remote command execution v Enabling the IVM for remote command execution
Metrics show no data available

Problem
Any of the following metrics available in Navigate Resources are reporting no data available: CPU Utilization %, Processors, Memory (MB), Entitled Processing Units.
Explanation
The unavailable metric data could be the result of any of the following items: v The version of Hardware Management Console or Integrated Virtualization Manager running on your systems might be unsupported. v Secure Shell (SSH) might not be correctly enabled on the platform manager for remote command execution. v The system inventory might not be current. v A particular data metric might not be supported on a particular system.
Resolution
To attempt to resolve the problem of metric data not appearing for Power Systems in IBM Systems Director, complete the following steps: v Verify that your platform manager is running on a supported version. 1. To check the version of Hardware Management Console or Integrated Virtualization Manager that is running on the platform manager, right-click the platform manager and select Properties. 2. Ensure the version of Hardware Management Console or Integrated Virtualization Manager that is running on the platform manager is supported. Check the Virtualization software supported topic for more information. 3. If necessary, update the Hardware Management Console or Integrated Virtualization Manager to a supported version.
238
v Ensure you have enabled the platform manager for remote command execution by starting the SSH service. See the following topics for more information: Enabling the HMC for remote command execution Enabling the IVM for remote command execution v Review the topic, Viewing resources in the Virtual Servers and Hosts view, for more information about supported metrics on Power Systems. v Ensure your inventory is current. From the navigation pane of IBM Systems Director, click Inventory > View and Collect Inventory. After submitting the Collect Inventory request, wait several minutes for the data to refresh, and check the virtualization metrics again.
Unable to discover your HMC after upgrading the HMC

This problem affects version 7.3.1 or later, of the Hardware Management Console (HMC).
Problem
After upgrading your HMC to version 7.3.1 or later, you are unable to discover the HMC using IBM Systems Director.
Explanation Resolution
Open the Pegasus and SLP ports to enable IBM Systems Director to discover and manage the HMC. To open the ports, complete the following steps: 1. In the HMC Navigation Area pane, expand the affected HMC and expand HMC Management. Click Operations. 2. In the HMC Configuration pane, click Change Network Settings. 3. In the Network Settings window, click the LAN Adapters tab. 4. Select the LAN Adapter that is connected to your LAN and click Details. 5. In the LAN Adapter Details window, click Firewall Settings. The top pane displays the firewall ports that you can enable. 6. In the top pane, select Open Pegasus and click Allow Incoming. Open Pegasus is added to the bottom pane of enabled ports. 7. In the top pane, select SLP and click Allow Incoming. SLP is added to the bottom pane of enabled ports. 8. Click OK; then click OK again. 9. If a message window about restarting the HMC is displayed, click OK. After the HMC is restarted, the ports are enabled and IBM Systems Director Server can discover the HMC. Related information AIX Pegasus CIM server and providers
Extended management task not working when editing an HMC or IVM virtual server
This problem can affect virtual servers that are managed by Hardware Management Console or Integrated Virtualization Manager.
239
Problem
When you are using the edit virtual server task on a virtual server that is managed by Hardware Management Console or Integrated Virtualization Manager and you attempt to use the Extended Management task to launch the platform manager software, you receive the following message:
Authentication Error The userid must be specified.
Resolution
Close the error window, and try the Extended Management task again. The launched task problem should resolve on the second attempt and open the appropriate platform manager in a new window.
Launch-in-context feature fails after revoking access

This problem affects Hardware Management Console and Integrated Virtualization Manager.
Problem
This problem occurs after you successfully request access to an HMC or IVM and subsequently revoke access to the same HMC or IVM. Although you have revoked access, you will notice that the launch-in-context menus, such as HMC Management, Extended Management, and IVM Management, are still displayed as tasks for the HMC or IVM. If you try to launch any of these tasks, the following message is displayed:
Authentication Error The userid must be specified.
Explanation
If you still want to launch the tasks under the HMC Management, Extended Management, or IVM Management menus after revoking access to the HMC or IVM, you must configure credentials for the console access point for the HMC/IVM. For more information, see "Creating console access point credentials."
System state in IBM Systems Director does not reflect state displayed in HMC or IVM
This problem affects systems that are managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM).
Problem
IBM Systems Director does not display the same system state that HMC or IVM displays. For example, in Navigate Resources you notice that the State column for a virtual server (logical partition) displays Started. However, the same virtual server in the HMC interface displays Error.
Explanation
IBM Systems Director currently does not display the detailed system state changes that HMC and IVM display. This is a known limitation.
240
Resolution
You can access the most current system state information by using the instructions in the following table. Note: If the Access state on Navigate Resources shows Unknown or Offline, it is an indication that communication between the IBM Systems Director Server and the HMC or IVM has been lost.
Table 10. Instructions for accessing detailed state information Managed system Physical system or virtual server (logical partition) managed by HMC Virtual or physical server managed by IVM Instructions for accessing detailed state information In Navigate Resources, right-click the system and select Extended Management > Properties. In Navigate Resources, right-click the system and select Extended Management > Properties. If you are unable to access the Extended Management menu, you can use the Advanced System Management Interface to view system state information. Note: If the system is a Power Systems BladeCenter server, you can use the Advanced Management Module to access system state information.
IVM indicates No Access after successfully requesting access

This problem affects the Integrated Virtualization Manager (IVM) and the Virtual I/O Server with Common Agent installed.
Problem
You request access to the Integrated Virtualization Manager (IVM). The access state changes from No Access to OK, but then reverts back to No Access.
Resolution
To resolve the problem, request access to the Virtual I/O Server. After successfully requesting access to the Virtual I/O Server, the access states for both the Virtual I/O Server and the IVM should indicate OK. Note: Ensure that you use the same IBM Systems Director Server to request access to both the IVM and the Virtual I/O Server.
Unable to discover host system and virtual servers after requesting access to Virtual I/O Server
This problem affects the IBM Power System server, its hosted virtual servers including the Virtual I/O Server with Common Agent installed, and the Integrated Virtualization Manager (IVM).
Problem
You successfully request access to the Virtual I/O Server. The access state for the Integrated Virtualization Manager (IVM) platform manager changes from No Access
241
to OK. However, the IBM Power System server that hosts the IVM and the virtual servers managed by the IVM cannot be discovered.
Explanation
When you successfully request access to the Virtual I/O Server, the IVM is erroneously unlocked. In this situation, the IVM has limited functionality, which causes discovery of the host system and its hosted virtual servers to fail. Therefore, you need to remove the Virtual I/O Server and IVM from the Web interface, unmanage the Virtual I/O Server, and rediscover the IVM and Virtual I/O Server. This resolution ensures that the host system and virtual servers can be discovered and displayed in the Web interface.
Resolution
To resolve the problem, complete the following steps: Note: Ensure that you use the same IBM Systems Director Server to perform the following tasks on the IVM and Virtual I/O Server. 1. Remove the Virtual I/O Server and the IVM from the user interface. 2. Unmanage the Virtual I/O Server, which has the Common Agent installed, by completing the following steps: a. Log in to the operating system that represents the Virtual I/O Server. b. Run the following command to enter the root environment (unrestricted shell). The command in Step 2c must be run in the root environment.
oem_setup_env
c. Run the following command to unmanage the operating system:

/opt/ibm/director/agent/runtime/agent/toolkit/bin/configure.sh -unmanaged -force
d. Type exit to exit the root environment (unrestricted shell) and return to the restricted shell. Attention: Ensure that you exit the root environment (unrestricted shell). Running commands outside of the restricted shell can cause problems. 3. Discover the Virtual I/O Server and the IVM that you deleted in Step 1. 4. Request access to the IVM platform manager. Note: When you request access to the IVM, the access state might change from No Access to OK, but then revert back to No Access. To correct the access state for the IVM, you must request access to the Virtual I/O Server by continuing with the next step. 5. Request access to the Virtual I/O Server. After you have completed these steps, the host system and all of the virtual servers managed by the IVM should be discovered and displayed in the Web interface.
HMC events take a long time to reach IBM Systems Director

This problem affects Hardware Management Console (HMC) events.
242
Problem
You notice that events generated by the HMC take a long time to reach the event log in IBM Systems Director. The events can be delayed by 15 minutes or longer.
Explanation
IBM Systems Director creates a CIM subscription on any HMC that is managed by IBM Systems Director. The CIM subscription enables the HMC to route its events to IBM Systems Director. If a large number of CIM subscriptions accumulate on the HMC, performance is impacted and events can take a long time to reach IBM Systems Director. IBM Systems Director automatically removes the CIM subscriptions on an HMC when the HMC is deleted from IBM Systems Director. However, if IBM Systems Director is reinstalled multiple times and the HMCs are not deleted before each installation, the CIM subscriptions can accumulate on the HMC and cause delays.
Resolution
To remove the CIM subscriptions from the HMC, complete the following steps: Note: Complete the following steps in namespace root/ibmsd and namespace root/cimv2. 1. List all CIM handlers on the HMC by running the following commands: Note: The command cimsubscribe is installed with IBM Systems Director Server or Agent. For example, it can be found on AIX in the following path: /opt/ibm/icc/cimom/bin.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -lh
where hmc_ip_address is the IP address for the HMC and namespace is root/ibmsd.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -lh
where hmc_ip_address is the IP address for the HMC and namespace is root/cimv2. 2. Check the destination field of each CIM handler. The destination field should indicate the IBM Systems Director Server that is managing this HMC. However, if the destination field indicates a different IBM Systems Director Server, the CIM handler is not usable and should be removed. 3. List all CIM subscriptions on the HMC by running the following commands:
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -ls
where hmc_ip_address is the IP address for the HMC and namespace is root/ibmsd.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -ls
where hmc_ip_address is the IP address for the HMC and namespace is root/cimv2. Note the name of the filter and the name of the handler that is displayed in the output. 4. Remove all of the CIM subscriptions that subscribe to an unusable handler by running the following commands:
243
Note: When running the following commands, specify the filter name and the handler name that was displayed in the output in the previous step.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -ds -fn filter_name -hn handler_name
where hmc_ip_address is the IP address for the HMC, namespace is root/ibmsd, filter_name is the name of the filter, and handler_name is the name of the handler.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -ds -fn filter_name -hn handler_name
where hmc_ip_address is the IP address for the HMC, namespace is root/cimv2, filter_name is the name of the filter, and handler_name is the name of the handler. 5. Remove all of the unusable handlers by running the following commands:
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -dh -hn handler_name
where hmc_ip_address is the IP address for the HMC, namespace is root/ibmsd, and handler_name is the name of the handler that you want to remove.
cimsubscribe -l hmc_ip_address:5989 -s yes -n namespace -dh -hn handler_name
where hmc_ip_address is the IP address for the HMC, namespace is root/cimv2, and handler_name is the name of the handler that you want to remove.
Virtual server remains visible after deletion

This problem can affect virtual servers that are managed by Virtual I/O Server Version 2.1.1.
Problem
You have deleted a virtual server that is managed by the Virtual I/O Server, but when you check the Virtual Servers and Hosts view, the virtual server that you attempted to delete is still listed.
Resolution
1. In the IBM Systems Director interface navigation area, expand Inventory and then click View and Collect Inventory. 2. Collect inventory for the host system. 3. Check the Virtual Servers and Hosts view again to see if the deleted virtual server is now removed.
VMware VirtualCenter environment troubleshooting

These problems can occur when you use IBM Systems Director virtualization manager in a VMware VirtualCenter environment.
Password change does not disconnect VMware VirtualCenter 1.4

This problem affects VMware VirtualCenter 1.4 systems that have the IBM Systems Director virtualization manager subagent for VMware VirtualCenter installed.
Problem
Changing the administrator password on a VMware VirtualCenter version 1.4 system does not immediately disconnect that system in the IBM Systems Director Web interface.
244
Resolution
Complete the following steps to attempt to resolve the problem with credentials on the VMware VirtualCenter host: 1. Run the VMware VirtualCenter setup.exe program again on the system where VMware VirtualCenter is installed. a. From the installation menu, select Repair. b. Specify the new user name and password information. 2. Restart the VMware VirtualCenter server. Use Windows Control Panel to access Administrative Tools > Services. Right-click the VMware Service entry and select Restart. 3. Restart the IBM Systems Director virtualization manager subagent for VMware VirtualCenter by specifying the following from a command line: v Windows: Director\agent\runtime\agent\bin\endpoint.bat stop Director\agent\runtime\agent\bin\endpoint.bat start v Linux: Director/agent/runtime/agent/bin/endpoint.sh stop Director/agent/runtime/agent/bin/endpoint.sh start where Director is the path where IBM Systems Director is installed. The VMware VirtualCenter host should now be in a disconnected state to reflect the administrator password change now being recognized.
Platform manager object requires credentials, but unable to connect

This problem affects access to the platform manager.
Problem
A platform manager object states that credentials are required, but Security > Connect is not available in the right-click menu for the platform manager.
Explanation
This problem occurs when VMware VirtualCenter server has granted permission to IBM Systems Director to perform operations, but later, someone changes the user ID and password of the VMware VirtualCenter server so access to the platform manager is no longer available.
Resolution
Complete the following steps to resolve this problem: 1. In the IBM Systems Director navigation pane, click Navigate Resources to locate the platform manager that you want to authenticate to the VMware management interface for that system. 2. Select the platform manager, click Actions from the menu bar, and select Security > Disconnect. 3. Select the platform manager, click Actions from the menu bar, and select Security > Connect. 4. Type the new connection information for the platform manager in the Connect window.
245
Unexpected behavior after renaming farm groups

This problem affects normal behavior for a VMware VirtualCenter virtual farm.
Problem
Unexpected behavior occurs for a virtual farm in any instance of IBM Systems Director that is tracking activity on the virtual farm.
Explanation
This symptom can occur when a farm that is contained within a farm group is discovered in IBM Systems Director and later that farm group is renamed in VMware VirtualCenter.
Resolution
After a farm group is renamed in VMware VirtualCenter, you should disconnect and connect to the platform manager that contains the virtual farm object. For information, see Disconnecting from a platform manager.
Virtual server relocation

This problem affects virtual server relocation.
Problem
Failure codes 66 and 67 are returned even though relocation is enabled on the system that is running VMware ESX Server in a VMware VirtualCenter environment. Relocation menu options are available for virtual server objects even though VMotion is not enabled in VMware VirtualCenter.
Explanation
These failure codes can be returned and the relocation menu options can be available when IBM Systems Director does not have the most up-to-date information about relocation properties from the virtualization application. This situation occurs more frequently when multiple users are making changes to the properties. For example, relocation failure codes can be returned when relocation properties have been modified in VMware VirtualCenter while IBM Systems Director is running.
Resolution
Collect inventory for the platform manager using the All Inventory profile.
An application exception error, an insufficient permission error, or a connection error occurs

This problem affects communication with VMware VirtualCenter.
Problem
An application exception error, an insufficient permission error, or a connection error occurs when you use launch the VMware VirtualCenter client from IBM Systems Director.
246
Resolution
Make sure that VMware VirtualCenter server is installed by a user that has administrator privileges on the installing system. If it was installed by a user that does not have administrator privileges, you either must assign administrator privileges to that user or reinstall VMware VirtualCenter server with a user that does have administrator privileges.
A login failure occurs when you try to connect to a platform manager

This problem affects communication with VMware VirtualCenter.
Problem
A login failure occurs when you try to connect to a platform manager.
Resolution
Make sure that the user that is running VMware VirtualCenter server has administrator privileges in VMware VirtualCenter. If it does not, log in to the VMware VirtualCenter client as a user with administrator privileges. Then, add administrator privileges to the user that does not have administrator privileges. If the problem persists, you might need to reset the password for the user with administrative privileges. To reset the password complete the following steps: 1. Stop the following services: v VMware VirtualCenter Server v VMware VirtualCenter Web Service 2. Reset the password for the VMware VirtualCenter administrator using the following command:
Installation_path\vma.exe -update -username userid -password new_password
where Installation_path indicates the installation path for vma.exe, userid indicates the id of the administrator whose password you are changing, and new_password is the new password that you want to specify for the administrator. The default installation path for vma.exe is C:\Program Files\VMware\ VMware VirtualCenter\vma.exe. 3. Restart the services that you stopped before resetting the password.
Systems in IBM Systems Director sometimes do not match those configured

This problem affects communication with VMware VirtualCenter or VMware ESX Server 3.0 or later.
Problem
Systems in IBM Systems Director sometimes do not match those configured in VMware VirtualCenter or VMware ESX Server. For example, IBM Systems Director can display host systems under a platform manager after those hosts have been removed from VMware VirtualCenter control.
247
Resolution
Make sure that you understand that changes made to platform managers or their associated hosts outside of IBM Systems Director cannot be reflected in IBM Systems Director until connections have been made for a given platform manager. For information about connecting to a platform manager, see the Connecting to a platform manager topic. In the example scenario, from IBM Systems Director, a platform manager object and its host objects were discovered. Later, access to that platform manager was revoked and IBM Systems Director Server was shut down. Then, using VMware VirtualCenter, the hosts associated with that platform manager were removed from VMware VirtualCenter control. However, when IBM Systems Director is turned back on, IBM Systems Director continues to display the hosts associated with the platform manager. Once access to that platform manager is requested through VMware VirtualCenter, IBM Systems Director can update the display to reflect reality, which is that the hosts are no longer associated with that platform manager.
Virtual server power operations behave unexpectedly

This problem affects virtual server power operations in a VMware VirtualCenter environment.
Problem
Virtual servers do not shut down and turn off as expected; instead, they turn off without an orderly shut down of their operating system or they remain in a transition state.
Resolution
Install VMware Tools in the virtual server so that shut down and turn off operations do not immediately turn off a virtual server without an orderly shut down. For information about installing VMware Tools, see the VMware VirtualCenter documentation. However, even when VMware Tools are installed, shut down and turn off operations are not completed as expected from IBM Systems Director. The guest operating system is shut down in an orderly way, but the virtual server is not turned off. You must perform an additional operation to turn off the virtual server. Complete the following steps to perform a shut down and power off of a virtual server: 1. Perform a shut down and power off operation for the virtual server. For information, see the topic, Managing power operations for a single virtual server. This action shuts down the operating system in an orderly way, but does not power off the virtual server. 2. Perform a second operation to turn off the virtual server. This second operation can be either another shut down and power off operation or a power off now operation. Note: Before performing a power off now operation, make sure that the operating system has completely shut down on the virtual server. One way to check this from IBM Systems Director is to establish a remote session on the virtual server.
248
Power operations on virtual servers that have multiple undoable disks sometimes fail
This problem affects virtual server power operations.
Explanation
Power operations on virtual servers that have multiple undoable disks sometimes fail.
Resolution
This symptom occurs infrequently, but happens when the IBM Systems Director virtualization manager subagent for VMware VirtualCenter fails to answer all the questions from VMware VirtualCenter about the power operation. If this symptom occurs, use the VMware VirtualCenter client application to answer any pending questions.
Unable to perform tasks on VMware VirtualCenter hosts in IBM Systems Director

This problem affects hosts that are under the control of VMware VirtualCenter.
Problem
Hosts that are managed by VMware VirtualCenter are unavailable for certain tasks in IBM Systems Director. For example, the host does not appear in the topology view, or you might be unable to exit maintenance mode for the host.
Resolution
You might be experiencing this problem because the VMware VirtualCenter system has not been discovered in the IBM Systems Director environment. You can attempt to resolve the problem by adding the VMware VirtualCenter system to your IBM Systems Director environment: 1. In IBM Systems Director, expand Inventory, and click System Discovery. 2. Complete the required fields to discover the VMware VirtualCenter system. 3. Click Navigate Resources to locate the platform manager that you want to authenticate to the VMware management interface for that system. Select the platform manager, click Actions from the menu bar, and select Security > Connect. 4. After the VMware VirtualCenter system is discovered, you can attempt your desired task again.
Unexpected problems when managing hosts under control of VMware VirtualCenter

This problem affects hosts that are under the control of VMware VirtualCenter.
Problem
When you attempt to use IBM Systems Director to perform a management task on a host that is managed by VMware VirtualCenter, you receive a failure message. For example, you might perform a relocation of a virtual server and receive an event with a command code of 161 and an error code of 24:
API exception occurred
249
Investigation
Use the VMware Infrastructure Client to attach to the VMware VirtualCenter system and use the inventory navigation to find references to the host. A potential cause for the problem might be that the host is defined two different times in VMware VirtualCenter. One reference is in a disconnected state and the other reference is in an active state.
Explanation
The application programming interface (API) that IBM Systems Director uses returns the first representation of the host that it finds. If the first host happens to be the disconnected representation, error code 24 will occur. IBM Systems Director is unable to manage VMware VirtualCenter hosts that are in the disconnected state.
Resolution
Use the VMware Infrastructure Client to attach to the VMware VirtualCenter system and remove the disconnected representations of the host that is receiving an error in IBM Systems Director.
Connect task fails on VMware VirtualCenter 1.4.x system

The problem affects using the Connect task on a VMware VirtualCenter 1.4.x system in the IBM Systems Director 6.1 environment.
Problem
After installing the Common Agent, you install the virtualization manager subagent for VMware VirtualCenter 1.4.x, using the following path: Release Management > Agents > Common Agent Subagent Packages > CommonAgentSubagent_VSM_VC14x-6.1.0. After the subagent is installed, you attempt the Security > Connect task, but the task fails.
Explanation
VMware VirtualCenter version 1.4.x is not a supported virtualization environment for IBM Systems Director 6.1. However, the virtualization manager subagent for VMware VirtualCenter 1.4.x is available for installation in IBM Systems Director 6.1. Because VMware VirtualCenter version 1.4.x is not supported in the IBM Systems Director 6.1 environment, you will be unable to successfully complete the Connect task.
Xen virtualization troubleshooting

These problems can occur in a Xen virtualization environment.
Xen virtual server relocks after you request and obtain access to it
This problem affects Xen virtual servers.
Problem
After you request and obtain access to a Xen virtual server using IBM Systems Director, the virtual server relocks for no apparent reason. For example, you request and obtain access to Xen virtual server A. Then, you request and obtain access to Xen virtual server B. You might not be aware that Xen virtual server A has relocked. Later, when you view or try to access Xen virtual server A, you are
250
puzzled because Xen virtual server A is locked.
Explanation
This problem can occur if you create a master image by running the image creation script manually, and then use the master image outside of IBM Systems Director before you use it with the Create Virtual Server wizard. Using the image with IBM Systems Director involves running the Create Virtual Server wizard and booting the virtual server at least once to complete the virtual server image creation process properly. When you use the image manually (outside of IBM Systems Director) the first time you create and boot a virtual server, the image is configured as part of that process and can no longer be used as a master image in IBM Systems Director.
Resolution
You need to clean up certain settings in the image to enable the existing image for use as a master image in IBM Systems Director. For more information, see the topic, Creating a customized master image for a Xen virtual server manually.
Only seven Xen virtual servers start at one time

Problem
When you try to start more than seven Xen virtual servers in addition to the host system IBM Systems Director, a total of only eight machines can be started.
Explanation
By default Linux only allows seven virtual servers in addition to the host.
Resolution
You can adjust the max_loop setting on the Xen host if you want to allow more virtual servers. You also need to create additional loop devices.
Inactive Xen virtual server does not appear in YaST or xm tools

This problem affects an inactive Xen virtual server.
Problem
An inactive Xen virtual server does not appear in the YaST tool or xm tool.
Resolution
This problem occurs because when you create a Xen virtual server using IBM Systems Director, the configuration information about the virtual server is stored in a directory that the YaST and xm tools do not recognize unless the virtual server is powered on.
251
Resolution
Power on the Xen virtual server. Right-click the Xen virtual server and select Power and Energy > Power On. Then, view the Xen virtual server using the YaST or xm tool.
Unable to power on Xen virtual server

Problem
When you try to power on a Xen virtual server in IBM Systems Director Server, the task fails and you see one of the following messages: v An unexpected error occurred attempting to execute the task v The execution task window is displayed indicating that status is pending. After approximately twenty seconds, a message is displayed indicating that the process failed. This problem can occur for one or more of the following reasons: v There is insufficient memory available on the Xen host system for the virtual server to use. v The image that you used to create the virtual server is invalid or corrupt. v The network has been configured incorrectly. v You have reached the maximum number of virtual servers allowed on the system because there are no more loop devices available for file-backed VBD.
Resolution
Use the following table to identify the potential problem and suggested action:
Table 11. Problems and suggested actions Problem There is insufficient memory available on the Xen host system for the virtual server to use. Suggested action Determine the amount of memory available on the host system and if sufficient memory is not available for the new virtual server that you are trying to start, free up the required amount of memory on the host system by shutting down one or more virtual servers, as appropriate.
252
Table 11. Problems and suggested actions (continued) Problem The image that you used to create the virtual server is missing, invalid, or corrupt. Suggested action Complete the following steps: 1. Determine whether the image file exists in the following directory: /var/opt/ibm/vm/domains/Virtual_Server_Name where Virtual_Server_Name is the name of the virtual server that you want to power on. If the image file exists in the directory, continue with the next step. If the image file is missing, you need to delete the virtual server and create a new one. 2. Determine the condition of the image by running the file command on the image file. The output should indicate that the image is of type x86 boot sector. For example, run the following command: file Virtual_Server_Name where Virtual_Server_Name is the name of the virtual server that you want to power on. The following sample output indicates that the image is not corrupt: vm1: x86 boot sector If the output indicates that the image is not of type x86 boot sector, you need to delete the virtual server and create a new one. The network has been configured incorrectly. You need to troubleshoot your network configuration by completing the following steps: 1. Determine whether the default bridge xenbr0 exists by running one of the following commands: v brctl show Verify in the output that xenbr0 is listed as a bridge. v ifconfig -a Verify that xenbr0 is listed as a network interface. 2. If the default bridge xenbr0 does not exist, you need to create a Xen bridge by running the following command: /etc/xen/scripts/network-bridge start
You have reached the maximum number of virtual servers allowed on the system because there are no more loop devices available for file-backed VBD.
By default Linux only allows seven virtual servers in addition to the host. You can adjust the max_loop setting on the Xen host if you want to allow more virtual servers. You also need to create additional loop devices.
Xen managed objects appear after CIM Provider is uninstalled

This problem affects the Xen host system.
253
Problem
You removed the Xen CIM RPM and promoted the Platform Agent to Common Agent, but Xen managed systems still appear in IBM Systems Director with tasks that cannot be completed.
Resolution
To remove the IBM Systems Director virtualization manager tasks from the Xen managed system context menu, you must manually remove the Xen managed system and rediscover it. Complete the following steps: 1. Right-click the Xen managed system and select Remove. 2. Rediscover the Xen system. In the navigation area, expand Inventory and click System Discovery. Specify the requested parameters for the system that you are adding and click Discover.
Problems when relocating a Xen virtual server

This problem affects Xen hosts and virtual servers.
Problem
One or more Xen virtual servers do not relocate successfully.
Investigation
Complete the following checks to ensure the virtual server can be relocated: 1. Ensure that the processor architecture on the source host and the target host is the same. v A virtual server running on a 32-bit host can only be relocated to another 32-bit host. Likewise, a virtual server running on a 64-bit host can only be relocated to another 64-bit host. v The processor model on the source host must match the processor model on the target host. To determine the processor models for the hosts, run the following command on both the source and target hosts:
# grep "model name" /proc/cpuinfo
For an AMD processor you might see something similar to the following output:
model name : Dual-Core AMD Opteron(tm) Processor 2216 HE.
For an Intel processor you might see something similar to the following output:
model name : Intel(R) Xeon(R) CPU 5130 @ 2.00GHz
2. Ensure that the DNS configuration is configured correctly so that the destination host can be reached from the source host, as well as the reverse. You can use one of the following strategies to ensure that the DNS is configured correctly: v Configure the hostname of both systems to be the fully qualified host and domain name using the following command on the source host:
hostname source_host_name.domain
where source_host_name is the name of the source host. Use the following command on the destination host:
254
hostname destination_host_name.domain
where destination_host_name is the name of the destination host. v Add an entry in the host file of the source system that maps the host name of the destination host to its IP address. Repeat this task for the source host on the destination host. v Ensure that the domain associated with each host is in the list of domains searched when resolving host names to IP addresses by adding the appropriate entry in the /etc/resolv.conf file. For, example add search domain.com for your domain. 3. Ensure that the source host and destination host are using the same bridge. You can use the following command to display the bridge that the system is using, as well as which adapters are connected:
$ brctl show
If the bridges do not match, relocation will not be possible. A potential reason for why the bridges do not match is described here. The host is multi-homed and the default route is configured to use a different port than the source host. For example, if system A is using eth0 and system B is using eth1 as its default route, the hosts will be using different xen bridges: xenbr0 and xenbr1 respectively. You can find information about how to modify the Xen bridge configuration by examining the following files: v /etc/xen/scripts/network-bridge v /etc/xen/xend-config.sxp 4. Check that the virtual server image is available on a shared storage volume, with that volume mounted by both the source and destination host. The mount point must be the same. 5. Ensure that the source host and the destination host have memory available that is equal to or greater than the virtual server or virtual servers that you want to relocate. 6. Ensure that the virtual server is not in an offline, stopped, or paused state.
Relocation fails with high processor and memory utilization

This problem affects Xen hosts and virtual servers.
Problem
When you attempt to relocate a Xen virtual server during periods of high processor utilization, coupled with high memory usage over long periods of time (several hours or more), the relocation fails. This problem may also occur when running Validation Compatibility to see if virtual servers are compatible to be relocated.
Resolution
You might need to restart the CIM daemons on both the source and target hosts to enable the virtual servers to be relocated successfully. You can check the CIM status with the following command:
/etc/init.d/cimserverd status
You can restart the CIM daemons with the following command:
255
/etc/init.d/cimserver restart
Unable to discover Xen virtual server created outside of IBM Systems Director
This problem affects the Xen virtualization environment.
Problem
You created a Xen virtual server using the YaST graphical user interface, or another tool, and you are unable to discover the virtual server using IBM Systems Director.
Explanation
This problem occurs because virtual servers created with tools other than IBM Systems Director cannot be managed with IBM Systems Director.
Resolution
You must use IBM Systems Director to create Xen virtual servers that can be managed in the IBM Systems Director environment.
Unable to log in to a virtual server after relocation

This problem affects virtual servers running Red Hat Enterprise Linux in a Xen virtual server environment.
Problem
You are unable to log in to the Xen virtual server in the following scenario: v The virtual server has been relocated more than two times. v The previous console session of the virtual server was entered by using the xm console command. v The previous console session of the virtual server was exited by pressing the key combination Ctrl + ].
Explanation
The security policy for system console login on Red Hat Enterprise Linux prevents the console from being exploited from unknown control character input. If the login prompt finds these suspicious control characters, it will lock down the console login for about 60 seconds. After 60 seconds, the login prompt will accept new input. The control characters, Ctrl + ], used to exit the console session fall into the scope of suspicious exploitable control characters for Red Hat Enterprise Linux.
Resolution
Use one of the following methods to access the virtual server: v Wait for the lock on the login prompt to expire, about 60 seconds, and press Enter to get a new login prompt. v Log in to the virtual server using a method other than xm console. For example, log in through the remote telnet or ssh client, if the telnet daemon or ssh daemon is open for the virtual server. v Restart the virtual server. After the virtual server is restarted, log in at a new login prompt.
256
Xen virtual servers not discovered

This problem affects Xen virtual servers on a host with Common Agent installed.
Problem
You have discovered a Xen host system, but the associated virtual servers are not being discovered.
Explanation
Managing Xen virtual servers created with IBM Systems Director virtualization manager is supported only with Platform Agent. Common Agent does not support Xen virtual server discovery or management.
Resolution
To manage the Xen virtual servers associated with the Xen host, uninstall the Common Agent and install the Platform Agent instead.
Commands troubleshooting
This section provides information about problems and workarounds for command-line interface included in IBM Systems Director, including smcli, mpcli and soapcli.
Help and error messages for the smcli command display only in English
This problem exists in the IBM Systems Director Server when using the command line interface.
Problem
When using the command line interface on management servers running AIX and Linux, help and error messages for smcli command itself (not all IBM Systems Director 6.1 commands) does not display in Italian (it), Brazilian Portuguese (pt_BR), Chinese and Japanese locales. They display only in English.
Resolution
This is a known limitation of IBM Systems Director 6.1. To view help information for smcli in the desired language, use the man smcli command. Error and other messages for smcli also display only in English.
Unable to display man pages on SUSE Linux Enterprise Server 9.x

This problem affects only management servers running SUSE Linux Enterprise Server 9.x.
Problem
The Linux man pages are encoded in UTF-8. The man command in SUSE Linux Enterprise Server 9.x is not able to process UTF-8, and therefore cannot display the man pages.
257
Resolution
To get help for the smcli commands on SUSE Linux Enterprise Server 9.x, perform one of these procedures: v Use the smcli --help command_name command to get detailed information about the command, including the syntax, a description of the command, a description of the options and operands, error codes, and examples. v Convert all man pages to EUC-JP encoding. For example:
mkdir -p /tmp/man/man1 iconv -futf8 -teucjp /opt/ibm/director/man/ja/man1/command_name.1 /tmp/man/man1/command_name.1 man -M /tmp/man/ command_name >
Tip: Run the man command using the ja_JP.UTF-8 locale, which is a default when the primary language has been set to Japanese.
Unable to run a specific smcli command

Investigation
v Verify that you have the correct permissions and roles to run the command. The permission name for each command is the command name itself. There is also a permission category assigned to each permission. v Management servers running a new installation of Windows requires a C runtime DLL, mscvr80.dll, from Microsoft to run smcli commands. If this DLL is missing, you will see the following error when you attempt to run an smcli command:
The system cannot run the specified program.
You can obtain the DLL by downloading and installing vcredist_x86.exe from Microsoft at https://www.microsoft.com/downloads. v Verify that the management server satisfies the hardware and software requirements. For more information about hardware and software requirements for IBM Systems Director Server, see the IBM Systems information center at publib.boulder.ibm.com/infocenter/systems/topic/ com.ibm.director.plan.helps.doc/ fqm0_r_supported_hardware_and_software_requirements.html. v If you installed IBM Systems Director 6.1 on a machine on which IBM Director 5.20 or earlier was installed and uninstalled, update the registry keys: (Windows only) Change the following values in the HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Director\CurrentVersion registry key:
Root =install_root\IBM\Director\ Data=install_root\IBM\Director\data\
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). (Linux and AIX only) Edit the etc/ibm/director/twgserver/twgserver file and change following key-value pair:
TWG_ROOTDIR =/opt/ibm/Director
258
to
USMI_ROOTDIR =/opt/ibm/Director
Unable to run smcli commands from a directory other than install_root/bin

This problem affects management servers running AIX and Linux only.
Investigation
Verify that the following entry appears in the etc/ibm/director/twgserver/ twgserver file:
USMI_ROOT=/opt/ibm/Director
The above entry should be added to the file automatically during installation.
Unable to run a dircli command

Problem
Most dircli commands are supported in this release for compatibility with IBM Director version 5.20.
Investigation
v Verify that the dircli command that you want to use is supported in this release. Only dircli commands that manage managed-objects, groups, discovery and inventory, events, tasks and jobs, SNMP devices, and virtualization are supported. v Verify that the CLILEGACY environment variable is set it to a value of 1. Many smcli and dircli commands have the same name. By setting CLILEGACY to 1, you can run the commands using the dircli syntax and output format.
Disksize not valid error when using command line

This problem affects virtual server creation on VMware VirtualCenter hosts or VMware ESX Server hosts when using the command line.
Problem
You attempt to create a virtual server using a mkvsmvs or mkvs command similar to the following:
C:\>dircli mkvsmvs -a "name=my_vs, gos=11, cpu=2, memsize=132, disksize=10, net=vMotion" -H "IBM 8674 41X 78ND552"
You receive the following error message:

DNZCLI0203E : (Usage error) The attribute disksize is not valid. Use the --help option for more information.
However, the help option does not provide the necessary information to complete the command successfully.
259
Resolution
When you use the dircli command mkvsmvs, you must specify both the disksize attribute and the vmfs attribute (disk label). Example of the mkvsmvs command with disk size specified using the correct syntax:
dircli mkvsmvs -a "name=Greg, gos=11, cpu=2, memsize=132, vmfs=San, disksize=10, net=vMotion" -H "IBM 8674 41X 78ND552"
When you use the smcli command, mkvs, disk size must be specified with the diskvolumelabel attribute. In this case, the disk size and volume label are contained within the diskvolumelabel table. The syntax to specify a disk size of 8GB on the disk whose volume label is "Shared" is: diskvolumelabel[Shared]=disksize:8 Example of the mkvs command with the disk size specified using the correct syntax:
smcli mkvs -A "name=Paul, gos=11, cpu=2, memsize=132, diskvolumelabel[Shared]=disksize:8, net=vMotion" "IBM 8674 41X 78ND552"
You can run lsvrtcap to determine which attributes can be specified when creating a virtual server. For example, you can run the following command on the VMware ESX Server host named "IBM 8674 41X 78ND552".
C:>smcli lsvrtcap -c mkvs -A 11 "IBM 8674 41X 78ND552"
The output is similar to the following:
260
gos
Value: 11 Options:
Description: name Value: null Min: 1 Max: 80 Description:
11, 9, 10, 3, 2, 1, 13, 5, 6, 7, 8, 4 The operating system type of the virtual server.
The name of the virtual server to be created.
cpu
Value: 1 Min: 1 Max: 2 Increment: 1 IncrementType: LINEAR Description: The number of processors that can be assigned to the virtual server.
memsize Value: 128 Min: 128 Max: 544 Increment: 4 IncrementType: LINEAR Description: The desired amount of memory (MB) to be assigned to the virtual server. memunitsize Value: MB Options: MB Description: The unit to use for memory that is to be assigned to the virtual server. diskvolumelabel Options: Key, Volume Label, Disk Size [Shared] Shared 1 [San] San 1 [VMFS] VMFS 1 net Value: vMotion Options: vMotion Description: The network label to be assigned to the virtual server.
Note: For gos, guest operating system options, the numbers map to the following operating systems: v 1 Windows 2000 Server v 2 Windows 2000 Professional v 3 Window2 2000 Advanced Server v 4 Windows XP Professional v 5 Windows Server 2003 Enterprise v 6 Windows Server 2003 Standard v 7 Windows Server 2003 WE v 8 Windows Small Business Server 2003 v 9 Novell Netware 5 v 10 Novell Netware 6 v 11 Linux v 13 Windows NT Server
261
Using the sample output, you can run the mkvsmvs command specifying vmfs=San and disksize=10 to create a 10GB disk on the disk labeled "San". See the following example:
C:>dircli mkvsmvs -a "name=Greg, gos=11, cpu=2, memsize=132, vmfs=San, disksize=10, net=vMotion" -H "IBM 8674 41X 78ND552"
Alternatively, you can run the mkvs command specifying diskvolumelabel[Shared]=disksize:8 to create an 8GB disk on the disk labeled "Shared". See the following example:
C:>smcli mkvs -A "name=Paul, gos=11, cpu=2, memsize=132, diskvolumelabel[Shared]=disksize:8, net=vMotion" "IBM 8674 41X 78ND552"
To verify whether the disk is created with the size requested, use the dircli command, lsvsm or the smcli command, lsvrtsys. See the following example for lsvsm:
C:>dircli lsvsm -l Greg
The lsvsm command displays output similar to the following:

0x12e6, Greg Configuration Path, [] /home/vmware/Greg/Greg.vmx Virtual Disk Type, Persistent Host Type, ESX Virtualization Parent, IBM 867441X 78ND552 Virtual Disk PowerOn Action, Commit CPU Count, 2 Memory Size (MB), 132 Restrict Virtual Server Movement, Not set Restart Priority, Not set Virtual Disk PowerOff Action, Commit Vendor Display Name, Greg Disk Size (GB), 10
See the following example for lsvrtsys:

C:\>smcli lsvrtsys -l Paul
The lsvrtsys command displays output similar to the following:

Paul: Configuration Path : [] /home/vmware/Paul/Paul.vmx Virtual Disk Type : Persistent Host Type : ESX Virtualization Parent : IBM 867441X 78ND552 Virtual Disk PowerOn Action : Commit CPU Count : 2 Memory Size (MB) : 132 Restrict Virtual Server Movement : Not set Restart Priority : Not set Virtual Disk PowerOff Action : Commit Vendor Display Name : Paul Disk Size (GB) : 8
Unable to change the language (locale)

This problem affects management servers running AIX only.
Investigation
v You can specify the language in several ways in the listed order of precedence: -L | --lang language option in the smcli command syntax DIR_LANG environment variable Operating-system language settings
262
Note: The -L | --lang option and the DIR_LANG environment variable are being deprecated in a future release of IBM Systems Director. Use of the -L | --lang option after it is deprecated will result in a usage error. If the DIR_LANG environment is set after it is deprecated, it will be ignored. v Verify that the specified language is supported. de: German en: English es: Spanish fr: French it: Italian ja: Japanese ko: Korean pt_BR: Brazilian Portuguese zh_CN: Simplified Chinese zh_TW: Traditional Chinese Tips: If you specify the language using the format language_country, where language is a supported language but country is a not a supported country code for that language (for example, en_US), then the specified language is used (for example, in this case en would be used). An error will not be displayed. If you specify a language that is not supported, irrespective of country code, the default language is used and an error message will be displayed.
Unable to use double-byte character set languages in AIX

This problem affects management servers running AIX only.
Problem
You are unable to use double-byte character set languages (such as Chinese, Japanese and Korean) when running smcli commands from a management server running AIX .
Investigation
1. If you are running commands from a remote system, verify that the remote system supports the desired double-byte character set by entering this command from a command line:
locale -a
2. Determine whether required fonts are present on the management server: a. From a command prompt, enter these commands:
export LC_ALL=language export LANG=language
Where language is a double-byte character set language (for example, ja, ko, zh_CN, or zh_TW).. b. Change to the install_root/usr/lib/X11/fonts/ directory, where install_root is the root directory of your IBM Systems Director installation. c. Enter this command:
grep monotype-sansmonowt- fonts.dir
You should see these two lines in the output. If the lines are not present, then required fonts are missing on the management server.
gb18tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-gb2312.1980-0 rom9tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-iso8859-1
263
Resolution
1. If you are running commands from a remote system, change the system language settings to the desired language. 2. To enable the use of the required fonts, change to the JAV A_HOME/lib directory from a command line and enter these commands:
mv font.properties.zh font.properties.zh.orig cp font.properties.zh.4.3.3 font.properties.zh
You can find more information about problems using double-byte character set languages on the Web at:www.ibm.com/developerworks/java/jdk/aix/118/ README.html
Output is empty for system and inventory commands

Problem
When you run system or inventory commands, no output is displayed.
Explanation
Before you can run any system command, such as lssys, you must first discover systems using the discover command. If no systems have been discovered, the output of the lssys command will be empty. Before you can run the lsinv command, you must first collect inventory for the targeted systems by running collectinv command. If no inventory has been collected, the output of the lsinv command will be empty.
Resolution
Run the discover command to discover all manageable systems, and run collectinv to collect inventory for the targeted systems.
Unable to connect to the CLI daemon

Problem
When running an smcli command, the following error is displayed:.
DNZCLI0129E : (Error) Could not connect to CLI daemon
Explanation
When the IBM Systems Director Server starts, it creates a file named CLISocketKey.dat at root\data folder. This file is required for smcli to communicate with IBM Systems Director Server. The error is displayed when IBM Systems Director Server started and the CLISocketKey.dat has not yet been created.
Resolution
Wait a few minute, and then run the command again.
264
genevent command troubleshooting

This section provides information for specific problems and workarounds associated with the genevent command. Some genevent command problems actually might be problems with IBM Systems Director components. Review all troubleshooting topics for possible solutions.
genevent command cannot determine the system ID

This problem affects managed systems when attempting to send an event to IBM Systems Director Server using the genevent command.
Problem
The genevent command fails and displays the following error message:
Error: Genevent can not determine the system unique id.
Investigation
Check for the following possible causes: Using a Remote Desktop Protocol (RDP) session If you are using a Remote Desktop Protocol (RDP) session when issuing the Genevent command, this error is expected and the command will fail. Try issuing the genevent command from the local management console. Cloned instances of Common Agent (Platform Agent managed systems) When cloning systems with Common Agent installed, do not start Common Agent on the system to be cloned until after it has been cloned. If started before cloning, Common Agent will calculate a unique ID for the system, which will be copied to any clones, resulting in multiple systems with the same "unique" ID and problems with IBM Systems Director Server. If this problem occurs on a managed resource running Windows, complete the following steps to resolve the problem: 1. To stop Common Agent, type the following command on the managed resource and press Enter:
net stop twgipc
2. Delete the following two files (paths listed below are the default paths; change if IBM Systems Director is installed elsewhere on your system):
C:\Program Files\IBM\Director\data\twgmach.id C:\Program Files\IBM\Director\data\netdrvr.ini
3. Delete the registry key hklm\system\currentcontrolset\control\ computername\computername\twgmachineid. 4. To open the Network Driver Configuration window, type the following command and press Enter:
twgipccf
5. Verify that the correct computer name and protocols are enabled. For more information about this step, see information about installing Common Agent on Windows using the InstallShield in the IBM Systems Director Planning, Installation, and Configuration Guide for your system. 6. To re-start Common Agent, type the following command and press Enter:
net start twgipc
265
7. Using IBM Systems Director Web interface, re-add the system for management by IBM Systems Director Server. 8. Try issuing the genevent command again.
Genevent found an error while communication with the management server

This problem affects systems when attempting to send an event to IBM Systems Director Server using the genevent command.
Problem
When attempting to send a Director > Topology > Online event to IBM Systems Director Server to add a Common Agent managed system, the genevent command fails and displays the following error message:
Genevent found an error communicating with the server.
Investigation
Complete the following troubleshooting steps until the problem is resolved. 1. Check the syntax of the genevent command you entered. The syntax is listed briefly below: a. If you have not used the /dest argument, try the command with the /dest argument specified. b. Check that the protocol and server_address values are correct. If the management server on which IBM Systems Director Server is installed has more than one network interface card (NIC), protocol must specify which NIC is being used. If the problem is not resolved, continue to the next step. 2. Run the genevent command again. If the problem is not resolved, continue to the next step. 3. Restart Common Agent. Type net stop twgipc and press Enter, and wait for the command to complete. Then, type net start twgipc and press Enter to restart Common Agent. 4. Run the genevent command again. If the problem is not resolved, continue to the next step. 5. Verify the network connectivity between the managed system and IBM Systems Director Server. Complete each of the following tests for connectivity: v Ping the management server on which IBM Systems Director Server is installed. Type ping server_address and press Enter. Verify that the management server responds. v Start a telnet session to the management server on port 14247. Type telnet server_address 14247 and press Enter. Verify that a telnet session is successfully started. 6. Try the genevent command again. If the problem is not resolved, continue to the next step. 7. Type twgreset -i and press Enter to reset Common Agent to its default configuration and erase the IBM Systems Director-assigned unique identifier for the managed system. 8. Try the genevent command again.
266
Additional strategies
If the previous troubleshooting strategies failed to resolve the problem, check for the following possible causes: Using a Remote Desktop Protocol (RDP) session If you are using a Remote Desktop Protocol (RDP) session when issuing the Genevent command, this error is expected and the command will fail. Try issuing the genevent command from the local management console. Cloned instances of Common Agent (Platform Agent managed systems) When cloning systems with Common Agent installed, do not start Common Agent on the system to be cloned until after it has been cloned. If started before cloning, Common Agent will calculate a unique ID for the system, which will be copied to any clones, resulting in multiple systems with the same "unique" ID and problems with IBM Systems Director Server. If this problem occurs on a managed resource running Windows, complete the following steps to resolve the problem: 1. To stop Common Agent, type the following command on the managed resource and press Enter:
net stop twgipc
2. Delete the following two files (paths listed below are the default paths; change if IBM Systems Director is installed elsewhere on your system):
C:\Program Files\IBM\Director\data\twgmach.id C:\Program Files\IBM\Director\data\netdrvr.ini
3. Delete the registry key hklm\system\currentcontrolset\control\ computername\computername\twgmachineid. 4. To open the Network Driver Configuration window, type the following command and press Enter:
twgipccf
5. Verify that the correct computer name and protocols are enabled. For more information about this step, see information about installing Common Agent on Windows using the InstallShield in the IBM Systems Director Planning, Installation, and Configuration Guide for your system. 6. To re-start Common Agent, type the following command and press Enter:
net start twgipc
7. Using IBM Systems Director Web interface, re-add the system for management by IBM Systems Director Server. 8. Try issuing the genevent command again.
Storage commands troubleshooting

This section provides information for specific problems and workarounds associated with the storage commands. Tip: v Ensure that inventory collection has been run on all discovered host systems, SMI-S providers, storage devices, and switches. Storage commands use collected inventory data to perform their function and therefore is required for successful operation.
267
v Some command problems actually might be problems with IBM Systems Director components. Review all troubleshooting topics for possible solutions.
Strategies for solving problems with storage commands

This problem affects storage commands that target host systems.
Resolution
For troubleshooting information, view the install_root\log\SSPTAudit.log file, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). You also can view the audit log file in IBM Systems Director Web interface. Click Options > Auditing Administration. In the Auditing Administration window, click View audit log. The audit log records a history of time stamps when storage commands are run. The history is recorded for task such as:: v Logging into IBM Systems Director Server v Viewing the storage audit log file v Activating a task v Deactivating a task The following example illustrates an audit log error entry:
"July 23 2008 3:39:45 PM, Command line interface, , , IBM Systems Director CLI Command Failed, CLI Command [lsnsvol ] failed with error code [1], root, localhost, ,"
Cannot find Fibre Channel ports, SAS ports, or ISCSI name for the targeted host
Problem
When running any smcli storage command (such as lsnshost and mknspath), the following error is displayed:
Could not find any Fibre Channel ports, SAS ports, or ISCSI name for the host
Explanation
Before you can run any storage command, you must first collect inventory for the targeted host systems by running collectinv command. During inventory collection, data such as Fibre Channel and SAS port information is collected. Tip: Ensure the targeted host system is unlocked before collecting inventory.
Resolution
v Run the discover command to discover all manageable systems, and run collectinv to collect inventory for the targeted systems. v Ensure that the SMI-S provider for the storage device is unlocked. Run the lsnssys command to view the connection status to the storage device. It must be accessible for this command to work.
268
lsnssys command does not display storage systems in output

This problem affects the lsnssys command that targets storage systems.
Problem
When running the lsnssys command, the output does not list the storage systems that has been previously discovered. If the storage system is not shown in the output, then no storage provisioning can be performed on the targeted storage system.
Investigation
Verify that the storage system is a supported system. If the model is not supported, then the lsnssys command will not list information about that storage system.
Resolution
If the storage system is supported, verify that the model name property of the storage system is set to a valid value.
lsnssys lists storage systems as inaccessible

This problem affects the lsnssys command that targets storage systems.
Problem
When running thelsnssys command, the output shows the systemAccessible property as false for the targeted storage system.
Investigation
v Verify that the storage system is a supported system. v Verify that the provider for the storage system is up and running. You can do this by physically verify that the system is powered on or by pinging the IP address of the controllers. v Verify that any SMI-S or CIM provider is running on the storage system to ensure that the IBM Systems Director Server can manage the storage system.
chnsvol command is not supported

This problem affects the chnsvol command that targets storage systems.
Problem
Some storage systems support renaming existing volumes, and some do not. For example, DS3000, DS4000, DS6000 support renaming volumes. IBM BladeCenter SAS RAID Controller Module does not support renaming volumes. When a storage system does not support this action, an error message is displayed.
Resolution
Attempt to rename volumes only on storage systems that support the action.
SAN connection error is displayed

269
Problem
When running a storage command, the following error messages displays:
Native error: Please check the SAN connection: Error in device accessor. Message: com.ibm.sysmgt.sspt.storage. DeviceAccessorException: CIM method hardwareIDManagementInstance.DeleteStorageHardwareID threw exception. Message: org.sblim.wbem.cim.CIMException: CIM_ERR_FAILED(Remote exception at the CIMOM:cimprovider.exceptions. ProviderException Description: Delete Protocol Controller invalid parameter)
Resolution
v Restart the Engenio CIM provider. v The Engenio CIM provider has known issues when used at the same time as the SANtricity software. If you receive CIM errors using an Engenio provider, stop using the SANtricity software. If you used proprietary mechanisms, you must clean up the references.
Host type matching the requirements is not supported by storage system

Problem
When running the chnssys command, you receive the following error:
Exception: Host type matching the requirements is not supported by storage system system
where system is the storage system you specified in the chnssys command.
Explanation Resolution
v Ensure that the host-type keyword is listed as a valid type for the specified network storage device. Valid types can vary depending on the disk array. To check the supported values and also to list the supported values for all the storage systems in your configuration, run the lsnssys command. v Ensure that you are running this common on a supported storage system. The chnssys command is on valid only for the DS4000 family of storage systems. It is not supported for DS3000, DS6000 and Serial Attached SCSI (SAS) RAID Controller Modules.
Session limit out of resource errors

his problem affects storage commands that target host systems.
Explanation
If administrative security is not enabled for a managed Qlogic switch, issuing a series of storage commands might cause session limit out of resource errors. This might to occur if more than 15 storage commands are issued in a five-minute period. The problem occurs because with security disabled, session handles are not cleaned up until they time out after five minutes.
270
Resolution
To resolve this problem, enable the administrative security for the switch. See the switch documentation for information about performing this configuration.
Zone and zone set are present when zoning is disabled

Problem
A zone and zone set are still present even when zoning is disabled. This situation is evident when running the lsnshost command.
Resolution
Detaching the last zone in a zone set using the chnshost -D command might not remove the zone. You must manually clean up the zone and zone set by logging into the affected switch. See the switch documentation for information on performing a manual clean up.
Update commands troubleshooting

This section provides information for specific problems and workarounds associated with the update commands. Tip: Some command problems actually might be problems with IBM Systems Director components. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Systems Director Release Notes.
The importupd command fails with error message 'The specified file xyz was not found.'
The importupd command fails because it cannot find the file in the specified path.
Problem
Updates are not imported because the specified file path name was not found.
Investigation
Ensure that all path names that contain spaces are enclosed in quotes. Determine if the specified file path exists.
Resolution
Place quotes around the file path name, if it contains spaces. Ensure that the specified file path does exist.
The cleanupd command does not remove updates

When trying to remove an update using the cleanupd command, the update is not removed.
Problem
Trying to remove a single update using the cleanupd command with the -m and -u options does not remove the update.
271
Investigation
Run the lsupd command with the -a and -l options to see if the update is superseded by any other updates. Run the lsupd command with the -m option to see if the update is a collection that contains other updates.
Explanation
The update may be involved in a supersedes, requires, or federates relationship with another update and cannot be removed without using the cleanupd command with the -F (--force) option.
Resolution
Run the cleanupd command with the -F (--force) option.
Console logging and tracing

You can view and modify the configuration properties of the diagnostic trace service. This information pertains to logs and traces for the IBM Systems Director Web interface framework only; it does not pertain to your managed resources. If a problem occurs with the Web interface framework and you must contact your next level of support, your service provider, or an IBM Systems Director service representative, your service representative might ask you to adjust these configuration properties. To change the settings for console logging and tracing, in the IBM Systems Director navigation area, expand Settings and click Console logging and tracing.
Sensor logs and debugging

IBM Systems Director provides sensor logs for debugging IBM System x and xSeries servers running either Linux or Windows. Turning on one or more of these sensor logs can provide important information for IBM Technical Support. There are two ways to turn on logging: v Use a configuration file that activates a log file. v Create an empty log file that is activated automatically.
Activating a log file using a configuration file

A configuration file controls whether logging is enabled and defines the maximum .log file length. For each area of logging there is one configuration file to turned on. IBM Systems Director is shipped with four sensor logs turned on and therefore are four configuration files shipped with IBM Systems Director. You can create new configuration files to turn on additional logging. The following configuration files are shipped with IBM Systems Director and are already enabled for logging: v libipmi.cfg v libcommipmi.cfg v librsa.cfg v sensorw.cfg
272
To create a configuration file to enable additional logging, complete the following steps on the managed system on which you want to turn on logging: 1. Change to the following directory on the managed system: install_root\data\logging, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 2. If the configuration file for the log you want to enable was not shipped with IBM Systems Director, create the configuration file in the directory with the appropriate file name. To name the configuration file, use the file name of the log file that you want to enable. Use .cfg for the file extension. For example, if you want to create a configuration file for the AssetIDProvider.log file, name the configuration file AssetIDProvider.cfg. The following list provides all the valid configuration file names. v AssetIDProvider.cfg v BlueLightProvider.cfg v blinterface.cfg v libcommrsa.cfg v libibm_shrdevice.cfg v libibmutils.cfg v spcommon.cfg v spinterface.cfg v IPConfigProvider.cfg v IPConfigInterface.cfg v PFAProvider.cfg v PFAInterface.cfg v SELProvider.cfg v SELInterface.cfg v SensorProvider.cfg v SmartProvider.cfg v SmartInterface.cfg v raid_lsiadapter.cfg v scsi_smartadapter.cfg v ide_smartadapter.cfg 3. Open the configuration file and add the following lines:
log=enable maxlength=n
where n is the number (in MB) that you want to set for the maximum log length. 4. Save and close the file. 5. Stop Common Agent by typing the applicable command from the command line and pressing Enter.
Option Linux Windows Description install_root/bin/twgstop net stop twgipc
where install_root is the root directory of your IBM Systems Director installation. 6. (Windows only) Stop the winmgmt service by typing net stop winmgmt from the command line and pressing Enter. 7. (Windows only) Make sure that the Pegasus Provider Adapter process is stopped. Open the Windows Task Manager window and click the Processes
273
page. If the Pegasus Provider Adapter process is still running, select the process from the list and then click End Process. 8. Start Common Agent by typing the applicable command and pressing Enter.
Option Linux Windows Description install_root/bin/twgstart net start twgipc
where install_root is the root directory of your IBM Systems Director installation. 9. (Windows only) Start the winmgmt service by typing net start winmgmt from the command line and pressing Enter. Related information AIX Pegasus CIM server and providers
Activating logging by creating an empty log file

You can automatically activate sensor logging by creating an empty log file. Unlike using configuration files, you do not have to restart any services for the logging to take effect. The log files use a default maximum log length of 5 MB. IBM Systems Director ships with the following batch files that can create all of the supported log files on a managed system.
Operating system Linux Windows Batch file install_root\proddata\logging\createLogFiles.sh install_root\proddata\logging\createLogFiles.bat
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). In the batch file you can comment out log file names that you do not want to create and use the batch file to create multiple log files at a time. To create one empty log file to enable additional logging, complete the following steps on the managed system on which you want to turn on logging: 1. Change to the following directory on the managed system: install_root\cimom\logs, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 2. Create the log file in the directory with the appropriate file name. See Sensor logs for debugging for the log file names. 3. Save and close the file.
Sensor logs for debugging

IBM Systems Director provides a number of log files for logging debug information for sensors in an IBM Systems Director environment. The following log files are turned on by default for first failure data capture: v libipmi.log
274
v libcommipmi.log v librsa.log v sensorw.log IBM Technical Support will tell you which of the following log files to turn on to gather the applicable data for your problem: Asset ID Reads and writes computer asset information and reads computer details, component information, and firmware levels: AssetIDProvider.log BlueLight Controls the front panel blue light: v BlueLightProvider.log v blinterface.log IPConfig Reads and writes IP configuration information for service processors: v IPConfigProvider.log v IPConfigInterface.log PFA Predictive Failure Analysis (PFA) displays system DIMM information and generates events (alerts) if microprocessors (CPUs) or DIMMs are preparing to fail: v PFAProvider.log v PFAInterface.log Reads and clears the service processor event log: v SELProvider.log v SELInterface.log Reads the system environmental sensors and generates an event (alert) if something goes wrong: v SensorProvider.log v sensorw.log SMART Reads drive information and generates an event (alert) if a drive is preparing to fail. There is a separate log file for each type of physical interface: v SmartProvider.log v SmartInterface.log v raid_lsiadapter.log v scsi_smartadapter.log v ide_smartadapter.log v The following log files are used by the libraries that communicate with an Remote Supervisor Adapter or IPMI baseboard management controller (BMC) service processor. These libraries are shared by all the providers. libibm_shrdevice.log libcommipmi.log libipmi.log libcommrsa.log librsa.log spcommon.log spinterface.log v The libibmutils.log file serves the libraries that contain common code used by providers, interfaces, and service processor libraries.
SEL
Sensor
275
Getting help and support

If you need help, service, or technical assistance or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. This section contains information about where to go for additional information about IBM and IBM products, and whom to call for service, if it is necessary.
Finding information about IBM Systems Director problems

In addition to the IBM Systems Director information center, you can find information about problems and solutions in earlier editions of IBM Systems Director documentation, the IBM Systems Director forum, and the IBM Service Bulletin (RETAIN tip) index.
Available troubleshooting documentation for earlier versions of IBM Systems Director

To troubleshoot problems that are specific to earlier versions of IBM Systems Director, see the documentation for that version. Notes: 1. Printable PDFs for the different versions of the IBM Systems Director documentation are available from the IBM Systems Director Support Web page at www.ibm.com/systems/management/director/. 2. IBM Director versions 4.22 and earlier and all versions of 5.10.x are no longer supported. 3.
IBM Systems Director version 6.1.x Available troubleshooting documentation v IBM Systems Director version 6.1.x information center v Release Notes v Service Bulletin (RETAIN tips) index v IBM Director version 5.20.x information center at http://publib.boulder.ibm.com/infocenter/director/v5r2/ index.jsp v Release Notes v Service Bulletin (RETAIN tips) index
5.20.x
Accessing the IBM Systems Director customer forum

The IBM Systems Director customer forum provides a place for customers to share ideas and solutions for IBM Systems Director implementations. It serves as the forum for IBM Systems Director installations on all supported operating systems and hardware. Although participating in the customer forum does not guarantee an answer from an IBM representative, the forum community does include IBM employees that use IBM Systems Director. To access the forum you must sign in to the IBM developerWorks Web site and create a profile; there is no fee. The IBM Systems Director customer forum Web page is at www.ibm.com/developerworks/forums/ forum.jspa?forumID=759.
Accessing the IBM Service Bulletin (RETAIN tips) index

You an access the IBM Service Bulletin (RETAIN tips) index to view known problems and workarounds for IBM Systems Director.
276
Note: After November 21, 2008, RETAIN tips for IBM Systems Director and related plug-ins will no longer be created. All subsequent tips will be created as Technotes and will be available in the IBM Systems Director Knowledge Base at www.ibm.com/support/search.wss?rs=0&q=eServerOnDemandKBRCH&r=100 &sort=desc. All previous IBM Systems Director RETAIN tips will continue to exist and will not be migrated to Technotes. Complete the following steps to access RETAIN tips: 1. Navigate to www.ibm.com/support/us. 2. On this page, select Systems Management Software for Support Type. 3. Select your Product Family and click Go. 4. Select Troubleshoot. A list of service bulletins is displayed. These service bulletins are specific to IBM Systems Director on IBM BladeCenter and System x hardware. For IBM Systems Director articles about other hardware platforms, such as IBM Power and System z, complete the following steps: a. Navigate to www.ibm.com/support/us. b. On this page, type Director in the Search field and press Enter. A list of support articles is displayed. c. Type additional keywords in the Additional search terms field to narrow the search results.
Getting support information from the World Wide Web

On the World Wide Web, the IBM Web site has up-to-date information about IBM BladeCenter, IBM Power, System x, and System z products, services, and support. Use the following Web addresses for the applicable product information.
IBM product BladeCenter products IBM Power systems System x servers System z mainframes Web address www.ibm.com/servers/eserver/support/bladecenter/ www.ibm.com/servers/eserver/support/iseries/ www.ibm.com/servers/eserver/support/unixservers/ www.ibm.com/servers/eserver/support/xseries/index.html www.ibm.com/servers/eserver/support/zseries/
You can find service information for your IBM products, including supported options, at www.ibm.com/support/us. Also, you can find information about IBM Systems Director in the IBM Systems forum at www.ibm.com/developerworks/forums/forum.jspa?forumID=759.
Information to provide to the IBM Technical Support Center or IBM Systems Director customer forum
When looking for assistance, either from IBM Technical Support Center or in the IBM Systems Director customer forum, there is some basic information that you should provide.
System x, BladeCenter, and x86-based system information

Before you contact IBM for assistance, or append to the customer forum, you should gather the following information for the affected systems.
277
Note: Frequently, IBM uses information and logs generated by the Dynamic System Analysis (DSA) program to resolve problems. DSA is available from the Systems Management Web page at www.ibm.com/servers/eserver/xseries/ systems_management/. v The machine types of all the affected systems. v The operating system. v The BIOS and firmware version levels of the affected systems. If you do not know this information, you can use Dynamic System Analysis (DSA) to gather the information for you. v Whether the failure is intermittent or persistent. v The last time the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Systems Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Systems Director you upgraded. v The error and trace logs that are located in the install_root/lwi/logs directory, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). v If it is an installation problem, the install logs that are located in the standard system directories and the install_root/logs directory, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). The following table contains examples of the install logs that are located in the standard system directories.
Table 12. Examples of install logs and their default locations Linux install logs (v6.1) IBM Systems Director install log: /var/log/dirinst.log IBM Systems Director Platform Agent install logs: /var/opt/ibm/platform/log/install.log IBM Systems Director Platform Agent uninstall logs: /var/opt/ibm/platform/log/ uninstall.log Windows install logs (v6.1) IBM Systems Director install log: C:\Windows\dirinst.log IBM Systems DirectorPlatform Agent install logs: C:\Windows\platinst_*.log IBM Systems DirectorPlatform Agent uninstall logs: C:\Windows\platuninst_*.log
v If it a hardware failure or related issue, the hardware logs. For more information, see Providing hardware-log information in the IBM Systems Director Systems Management Guide. v If possible, the steps required to recreate the problem.
System i information
Before you contact IBM for assistance, or append to the customer forum, you should gather the following information for the affected systems: v The operating system information for management server and for the managed objects. v Whether the failure is intermittent or persistent. v The last time (or release) that the feature or function worked. v Any exceptions or error messages that occur.
278
v The version of IBM Systems Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Systems Director you upgraded. v If possible, the steps required to recreate the problem.
System p information
Before you contact IBM for assistance, or append to the customer forum, you should gather the applicable information for the affected systems. For AIX : v The files containing the redirected output from the following commands: oslevel -r lslpp -L lsdev prtconf errpt -a lsvpd v The error and trace logs that are located in the install_root/lwi/logs directory, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). v The /var/log/dirinst.log file, if you are having an installation problem. v Run the /opt/ibm/director/bin/logcollector script to acquire all the logs required for debugging. v Whether the failure is intermittent or persistent. v The last time the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Systems Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Systems Director you upgraded. v If possible, the steps required to recreate the problem. For Linux on Power Systems v The files containing the redirected output from the following commands: (For Red Hat Enterprise Linux) cat /etc/redhat-release (For SUSE Linux) cat /etc/SuSE-release rpm -qa lsvpd v The error and trace logs that are located in the install_root/lwi/logs directory, where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). v The /var/log/dirinst.log file, if you are having an installation problem. v Run the /opt/ibm/director/bin/logcollector script to acquire all the logs required for debugging. v Whether the failure is intermittent or persistent. v The last time the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Systems Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Systems Director you upgraded. v If possible, the steps required to recreate the problem.
279
System z information
Before you contact IBM for assistance, or append to the customer forum, you should gather the applicable information for the affected systems. v A detailed description of the problem. v Any exceptions or error messages that occur. v If possible, the steps required to recreate the problem. v Whether the failure is intermittent or persistent. v The operating system information for the management server and for the managed resources. v The version of IBM Systems Director that is installed in each affected system. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Systems Director you upgraded. v The /var/log/dirinst.log file, if you are having an installation problem. v The /var/log/localmessages or any related log file on manageability access point (MAP) for z/VM. v The /opt/ibm/director/log/TWGRas.log file on the management server.
Getting fixes
Occasionally, new releases and upgrades are made available from the IBM Support Web site at www.ibm.com/systems/management/director/. These releases and upgrades might contain fixes to problems with IBM Systems Director. If your IBM Systems Director environment has a problem that is not fixed by a new release or upgrade, contact the IBM Technical Support Center. To do so, you must have purchased an appropriate support product from IBM.
Service and support information

Service and support offerings for IBM Systems Director are based on the platform on which you choose to run IBM Systems Director Server. For IBM Systems Director Server running on IBM BladeCenter or System x systems, subscription services are available for a fee entitling you to notification of new upgrades, patches and support information, and free updates during that period. For more information about subscription services or to renew your subscription service contract, see the Ready to Buy Web Page at www.ibm.com/systems/management/director/subscription/. For more information about service and support offerings available for all IBM systems, see Support Offerings Web site at www.ibm.com/systems/support/ supportsite.wss/docdisplay?lndocid=MIGR-5076601&brandind=5000016 or contact your IBM representative or IBM Business Partner.
IBM Systems Director Web interface messages

Each IBM Systems Director Web interface message contains a unique identifier (for example, AVE0299E). You can use this identifier to find more detailed information in the IBM Systems Director help system. You can use the Search feature of the help system to search for help associated with your message. Copy and paste your message identifier into the Search field, and click Go. Note that not all messages have more detailed help associated with them.
280
All IBM Systems Director Web interface messages use the following criteria: v The entire message ID is 7 characters minimum and 10 characters maximum, in the format XXXYYY######Z. v The first three alphabetic characters (XXX) identify the prefix for component v The next 0-3 alphabetic characters (YYY) identify the subsystem. The subsystem ID is optional. v The next 3-6 digits (######) identify the message number. v The last character (Z) identifies the severity code. v Zero padded numbers are not unique. Numbers 29, 029, and 0029 are all the same.
281
282
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
283
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation MW9A/050 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common
284
law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/ copytrade.shtml. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Java and the Java logo are a trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Other company, product, or service names may be trademarks or service marks of others.
Notices
285
286
Printed in USA
GC30-4177-04

Director BK Troubleshoot

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Director BK Troubleshoot

Transféré par

Droits d'auteur :

Formats disponibles

IBM Systems

IBM Systems Director Troubleshooting and Support Guide

IBM Systems Director Troubleshooting and Support Guide

Troubleshooting and support . . . . . 1

Copyright IBM Corp. 1999, 2010

IBM Systems Director Troubleshooting and Support Guide

141 141 142 143 143

167 167 168 168 168 169

169 169 169 170

182 182 183

IBM Systems Director Troubleshooting and Support Guide

185 186 186 187 187

189 189 189

190 190 190

192 193 194 194 194 195

204 205 206 206 206 207 207 208 208

218 219 220 220 220 221 222

277 280 280 280

IBM Systems Director Troubleshooting and Support Guide

About this publication

Conventions and terminology

Publications and related information

Information centers and topic collections

Copyright IBM Corp. 1999, 2010

IBM Systems Director Troubleshooting and Support Guide

White papers and briefs

IBM Redbooks publications

IBM Systems Director Troubleshooting and Support Guide

How to send your comments

IBM Systems Director Troubleshooting and Support Guide

Troubleshooting and support

Limitations and workarounds

Copyright IBM Corp. 1999, 2010

Agent installation does not generate events

BladeCenter is offline after the AMM failed over

Command fails on smcli

IBM Systems Director Troubleshooting and Support Guide

Delete operations take a long time to complete

Error messages include placeholder text

Excessive windows prompting for undoable disk power actions

File Manager displays a blank table

IBM Systems Director Troubleshooting and Support Guide

File Manager fails to copy files larger than 1.5 GB

Help selection is a question mark

Troubleshooting and support

IBM Systems Director Troubleshooting and Support Guide

Capacity information is not correct for storage devices

Troubleshooting and support

The OID for different SNMP traps are the same

IBM Systems Director Troubleshooting and Support Guide

Limitations of large tables

Selections or data entered into fields is lost

Troubleshooting and support

Severe log entry in the trace log

The Severity column always reports Information

IBM Systems Director Troubleshooting and Support Guide

Switch does not respond to IP address change

In the IBM Systems Director Web interface

2. Change the IP address. 3. Discover the switch again.

Switch information is not accurate in IBM Systems Director Server

Troubleshooting and support

IBM Systems Director Troubleshooting and Support Guide