IBM Systems

IBM Systems DirectorTroubleshooting and Support GuideVersion 6.3.1

GC30-4177-05

���

IBM Systems

IBM Systems DirectorTroubleshooting and Support GuideVersion 6.3.1

GC30-4177-05

���

NoteBefore using this information and the product it supports, read the information in “Notices” onpage 239.

© Copyright IBM Corporation 1999, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . ixConventions and terminology . . . . . . . . ixPublications and related information . . . . . . ixWeb resources . . . . . . . . . . . . . xiiHow to send your comments . . . . . . . . xiii

Troubleshooting and support . . . . . 1Limitations and workarounds. . . . . . . . . 1

Discovery profile auto-unlock and auto-inventorynot supported for IBM Director Agent . . . . . 1Agent installation does not generate events . . . 2BladeCenter is offline after the AMM failed over . 2Changes to the network interface card (NIC)configuration cannot be deployed to operatingsystem resources . . . . . . . . . . . . 2Command fails on smcli . . . . . . . . . 3Common Agent and Platform Agent are notautomatically discovered after installation . . . 3Date and time remain editable after deselectingthe Power On Server . . . . . . . . . . 3Delete operations take a long time to complete . . 4Excessive windows prompting for undoable diskpower actions . . . . . . . . . . . . . 4File Manager displays a blank table. . . . . . 5File Manager fails to copy files larger than 1.5 GB 5Help selection is a question mark . . . . . . 5IBM Storage Configuration Manager (SCM) 2.10 orearlier does not support non-English operatingsystems . . . . . . . . . . . . . . . 6Limitations using IBM Systems Director tomanage resources behind a NAT firewall . . . . 6Capacity information is not correct for storagedevices . . . . . . . . . . . . . . . 7Table view entries do not include Linux operatingsystem version information . . . . . . . . 7Event Filter Builder tree displays multipleWindows event log nodes . . . . . . . . . 8The OID for different SNMP traps are the same . 8Removing a managed operating system does notremove the managed server . . . . . . . . 8Limitations of large tables . . . . . . . . . 9Selections or data entered into fields is lost . . . 9The Severity column always reports Information 9Warning message recorded after installing theSMbus or LM78 device driver . . . . . . . 10Switch does not respond to IP address change. . 10Brocade Fibre Channel switch has unexpectedstatus of Offline . . . . . . . . . . . . 11Switch information is not accurate in IBMSystems Director Server . . . . . . . . . 11IBM Systems Director Server might fail to start inIPV6-only environment on Linux platform . . . 12Tables are not displayed correctly . . . . . . 13The cimserver service stops . . . . . . . . 13Unable to filter events for virtual server failures 13

Virtual farm events are not filtered . . . . . 14Virtual farm view does not refresh when hostschange . . . . . . . . . . . . . . . 14Virtualization manager tasks fail to start inmulti-NIC environment . . . . . . . . . 15Add or Remove Programs displays an incorrectprogram size for Platform Agent . . . . . . 15Antivirus programs might conflict with certainIBM Systems Director processes . . . . . . 16Receiving alerts associated with an LSI 1030Controller . . . . . . . . . . . . . . 16Incorrect version listed for Common Agent 6.2.0.1on AIX . . . . . . . . . . . . . . . 17Cannot restart the OS for managed AIX 6 CAS 17Platform Agent events sent over SSL are notreceived . . . . . . . . . . . . . . 17Update manager limitations and workarounds . 18

Installation and migration troubleshooting . . . . 24AIX installation troubleshooting . . . . . . 25Linux installation troubleshooting . . . . . . 25VMware installation troubleshooting . . . . . 27Windows installation troubleshooting. . . . . 29Cannot connect to agents after migration from6.1.x to 6.2 . . . . . . . . . . . . . . 30Agents are not migrated during migration from6.1.x to 6.2 . . . . . . . . . . . . . . 30Cannot upgrade Common Agent from 6.2 to 6.3.xon IPv6-only managed system . . . . . . . 31Cannot install agent on managed system . . . 32Installing a version of IBM Systems Director thatis earlier than the current version . . . . . . 33IBM Systems Director installation hangs and thenfails . . . . . . . . . . . . . . . . 33IBM Systems Director installation oruninstallation fails and requires cleanup . . . . 34Network outage while installing IBM SystemsDirector Server . . . . . . . . . . . . 37Installation fails when contacting an agentmanager . . . . . . . . . . . . . . 38Uninstallation of Common Agent on SUSE LinuxEnterprise Server 9 for System x takesapproximately one hour . . . . . . . . . 38Silent installation does not verify settings beforeinstalling . . . . . . . . . . . . . . 39Configuration data is not preserved afteruninstalling IBM Systems Director on Linux onSystem x . . . . . . . . . . . . . . 39CIT service error displayed in Event Viewerwhen installing CAS agent on Windows Server2008 . . . . . . . . . . . . . . . . 39A return code with no message text is displayedwhen deploying Windows agent packages . . . 40

Unknown error message is displayed when usingSLES . . . . . . . . . . . . . . . . 40Database configuration troubleshooting . . . . . 40

© Copyright IBM Corp. 1999, 2012 iii

Errors occur during the Oracle Databaseconfiguration . . . . . . . . . . . . . 40ORA-00257 error from the Oracle Database . . . 41ORA-00604 error from the Oracle Database . . . 41Oracle Database 10g Release 2 administratorclient will not install on Red Hat EnterpriseLinux, version 5.0, or SUSE Linux EnterpriseServer 10 . . . . . . . . . . . . . . 42Oracle Database 10g Release 2 administratorclient installation on Linux on Power Systemsthrows errors . . . . . . . . . . . . . 44Unable to connect to the database . . . . . . 45Database data is not displayed after databaserestart . . . . . . . . . . . . . . . 47Poor Performance when the IBM SystemsDirector server is configured with Microsoft SQLServer 2005 configuration. . . . . . . . . 47smrestore fails when IBM DB2 is configured torequire approval of restore operation . . . . . 48

Problems logging in troubleshooting . . . . . . 49Unable to access Log in page for IBM SystemsDirector . . . . . . . . . . . . . . 49Logging into IBM Systems Director Server fails 50

IBM Systems Director Server troubleshooting . . . 51An IBM Systems Director Server manageableresource shows offline after discovering its agent . 51IBM Systems Director Server fails to start . . . 52IBM Systems Director causes network traffic . . 52IBM Systems Director Server not receiving eventindications. . . . . . . . . . . . . . 53IBM Systems Director Server restarts afterunstable conditions are detected . . . . . . 53Problems exist on IBM i systems with IBMDirector Agent version 5.20 installed . . . . . 53Trace and error log files are not created . . . . 54Uncertain if IBM Systems Director Server isrunning. . . . . . . . . . . . . . . 55User is locked out of IBM Systems Director. . . 55

Common Agent and Platform Agent troubleshooting 56Extraneous CIM indication errors appear in thesystem log on Linux . . . . . . . . . . 56Managed resource does not send events . . . . 57You cannot promote Platform Agent to CommonAgent on Linux with Xen. . . . . . . . . 57Cannot install agents on Red Hat EnterpriseLinux or VMware managed systems using theAgent Installation Wizard . . . . . . . . 58Cannot install agent on managed system . . . 58Common Agent cannot be installed on an AIX orLinux system . . . . . . . . . . . . . 59Installing Common Agent on managed systemswith IBM Director Agent version 5.20 does notsucceed. . . . . . . . . . . . . . . 61A discovered agent displays an unexpectedmanaged system. . . . . . . . . . . . 61Unable to upgrade L2 agent to Common Agenton VMware ESX Server 3.5 or Red Hat EnterpriseLinux 5.3 hosts . . . . . . . . . . . . 62

IBM Systems Director, version 6.1.1, PlatformAgent installed on systems with an IntegratedManagement Processor (iMM) requires anIntelligent Platform Management Interface (IPMI)driver . . . . . . . . . . . . . . . 62Platform Agent 5.20.3x installation fails onsystems with Citrix XenApp . . . . . . . . 63Common Agent does not start when the hostname is set to localhost or the name server is notsetup correctly . . . . . . . . . . . . 63Installation of the common agent on AIX fails tostart LWI . . . . . . . . . . . . . . 63IBM Director Agent version 5.20.x agentsautomatically change to offline state in IBMSystems Director 6.x . . . . . . . . . . 64Segmentation fault message is shown whenstopping the cimserver . . . . . . . . . 64DNS servers are overwritten in resolv.conf . . . 65Duplicate managed resources appear afterrelocating a logical partition from an AIX system . 66

Configure Agent Manager on IBM Systems DirectorServer . . . . . . . . . . . . . . . . 67Web interface troubleshooting . . . . . . . . 70

Certificate has not been signed by a trustedauthority . . . . . . . . . . . . . . 70Firebug Firefox extension might causeunpredictable behavior in the IBM SystemsDirector Web interface . . . . . . . . . . 73Inserting a variable in the Auto Rename templateappears to fail . . . . . . . . . . . . 73Internet Explorer fails to display the IBMSystems Director Web interface . . . . . . . 73Login message displays corrupt characters . . . 74No results found when using Find a Resource . . 74Panels display translated text in multiplelanguages . . . . . . . . . . . . . . 74Panels display truncated text in non-Englishlanguages . . . . . . . . . . . . . . 75Panels display truncated text in non-Englishlanguages . . . . . . . . . . . . . . 75Unpredictable results occur when users log intoIBM Systems Director Server using the samebrowser application. . . . . . . . . . . 75Unable to export information . . . . . . . 76Unable to print information . . . . . . . . 77The IBM Systems Director Web interface does notperform as expected when browsing . . . . . 77Resource Explorer views not refreshing properlyafter resources removed . . . . . . . . . 78Navigation area disappears when refreshing thebrowser screen . . . . . . . . . . . . 79Firefox stores user data across multiple browserinstances . . . . . . . . . . . . . . 79

Launched tasks troubleshooting . . . . . . . 80Contents of the launch[x].jnlp file are displayed 80Cannot start DS storage manager when usingWindows Internet Explorer 8 . . . . . . . 80A download window is displayed . . . . . . 81Empty window is displayed or nothing happens 82A host name mismatch is detected. . . . . . 83

iv IBM Systems Director Troubleshooting and Support Guide

Java Web Start - Download Error window isdisplayed . . . . . . . . . . . . . . 84Java Web Start fails because correct IP addresscannot be determined . . . . . . . . . . 85Java Web Start fails due to JARS signed withmultiple certificates. . . . . . . . . . . 85Launched-tasks feature fails on System z system 86Message indicates a failure to validate certificate 86Message indicates that the application’s digitalsignature has an error . . . . . . . . . . 87Message indicates that the installation image forconsole cannot be found . . . . . . . . . 88Message states that Java Web Start is required . . 89Multiple Firefox browser windows open. . . . 89Opening launch.jnlp window is displayed . . . 89Storage application launch failure information . . 90Storage task unavailable for LSI Integrated RAIDController . . . . . . . . . . . . . . 91Unable to display the requested help . . . . . 91Unable to launch the application . . . . . . 92Unable to load resources . . . . . . . . . 94Windows fails to open a file . . . . . . . . 96

Accessibility troubleshooting, including JAWS . . . 96Accessible method for installing IBM SystemsDirector . . . . . . . . . . . . . . 96Preventing session timeouts for users withdisabilities . . . . . . . . . . . . . . 96Audible notification is not given for wizards inFirefox . . . . . . . . . . . . . . . 97Create Virtual Server wizard displays previouspage when pressing Enter in a text field . . . . 97Cursor disappears and page refreshes whenperforming virtualization manager tasks. . . . 98Focus is lost when clicking the Select All orDeselect All button . . . . . . . . . . . 98Identifying table filter row information usingJAWS . . . . . . . . . . . . . . . 98JAWS screen reader becomes mute . . . . . 99JAWS does not read Pre-Installation Utilitycontent . . . . . . . . . . . . . . . 99JAWS screen reader reads extra frame . . . . 100JAWS cannot read remote serial console output 100JAWS screen reader reads some Web interfaceelements incorrectly . . . . . . . . . . 100JAWS screen reader suggests incorrect keys forradio buttons in a table . . . . . . . . . 102JAWS screen reader reads the Next buttonincorrectly on some pages . . . . . . . . 102Keyboard navigation does not work in orbetween Selected and Available list boxes . . . 102Keyboard navigation does not work in someAction menus . . . . . . . . . . . . 103Language attribute not set properly in somepanels when using Internet Explorer . . . . 103Multiple read-only input text areas in samepage are read incorrectly by JAWS in Firefox . . 103The calendar is not usable or readable by theJAWS screen reader in forms mode . . . . . 104The Time field is not readable by the JAWSscreen reader . . . . . . . . . . . . 104

Unable to navigate to expanded content withtraditional key sequences when using JAWSscreen reader . . . . . . . . . . . . 105

Automation manager troubleshooting . . . . . 105A program fails to run when the eventautomation plans is triggered . . . . . . . 105Active Energy Manager threshold options arenot displayed in the Event Automation Planwizard . . . . . . . . . . . . . . 106The specified event does not trigger the eventautomation plan . . . . . . . . . . . 106An event automation plan is not triggered whenthe event filter uses extended details . . . . 107An SNMP trap or an SNMP inform request wasnot received . . . . . . . . . . . . . 109Automation plan not activated for virtual farmor relocation event. . . . . . . . . . . 109Cannot run Collect Inventory task using anevent action . . . . . . . . . . . . . 111Difficulty accessing event automation plansystem variables . . . . . . . . . . . 111E-mail fails to be sent. . . . . . . . . . 112Event actions fail . . . . . . . . . . . 113Target systems are lost when an eventautomation plan is imported . . . . . . . 113Event automation plans are not displayed . . . 114Event automation plans do not support somefeatures of earlier event action plans. . . . . 114Event automation plans do not work correctly 115Event not forwarded to Tivoli EnterpriseConsole event server . . . . . . . . . . 115Group members are not processed correctly instatic groups. . . . . . . . . . . . . 116IBM i message queue events do not triggerevent automation plans as expected . . . . . 116News fails to post to a newsgroup . . . . . 117Resource-monitor threshold settings changeunexpectedly . . . . . . . . . . . . 118SNMP traps do not contain message text . . . 118Start a program on a system event action fails 119Test results are missing for an event action . . 120Threshold values are no longer selected or arezeroed out in an event automation plan . . . 121Unfamiliar event filters are displayed on theEvent Filters page . . . . . . . . . . . 121

Configuration manager troubleshooting . . . . 121Configuration manager status is shown as NotReady in the Home page . . . . . . . . 122Mass configuration fails to configure Asset IDinformation . . . . . . . . . . . . . 123Deploy of a configuration template fails on atarget device that is not supported . . . . . 124

Discovery manager (including inventory)troubleshooting. . . . . . . . . . . . . 125

Discovery troubleshooting . . . . . . . . 125Inventory troubleshooting . . . . . . . . 135

Security and requesting access troubleshooting . . 140Handling Request Access failures. . . . . . 140Access request to IBM Director Agent 5.20 fails 143

Contents v

SNMP remote service access point of a switchgoes offline after switch creation and staysoffline after request access . . . . . . . . 144Request Access password length restriction . . 144Access request to a managed system runningSUSE Linux Enterprise Server fails . . . . . 145Agentless or Platform-Agent managed resourcecannot be accessed . . . . . . . . . . 146IsLocked property always shows false forcase-sensitive LDAP user names . . . . . . 146Managed resource state is Unknown . . . . . 147Credential mapping wizard does not finishwhen editing a credential mapping . . . . . 147Settings permission is not available to users ingroups other than smadmin . . . . . . . 148Hardware Management Console access statebecomes unknown after supplying incorrectcredentials . . . . . . . . . . . . . 148Trust domain users cannot log on . . . . . 149Spaces are not allowed for LDAP user full DN 149LDAP users unable to login when users in samepath exceed 500 . . . . . . . . . . . 149DN values for securityldap.properties mustmatch the LDAP server base values . . . . . 150

IBM BladeCenter and System x managementtroubleshooting. . . . . . . . . . . . . 150

Access is not granted automatically to switches 150IBM Systems Director cannot communicate without-of-band systems . . . . . . . . . . 151CIM protocol not discovered on systemsrunning ESXi operating system . . . . . . 152Configuration manager templatetroubleshooting. . . . . . . . . . . . 152Full access to a QLogic or Nortel switch is notpermitted with user ID and password . . . . 156The Hardware Log task is not available . . . 156Incorrect events reported for NICs that have ateaming configuration of active-standby . . . 157LED Status column is unavailable in ResourceExplorer . . . . . . . . . . . . . . 158LED Status column does not report hardwareproblems . . . . . . . . . . . . . . 159Out-of-band events are not configured correctly 159Out-of-band tasks fail on IPMI managedsystems . . . . . . . . . . . . . . 160Power tasks vary by the resource. . . . . . 161Predictive Failure Analysis events not reportedfor System x3755 M3 servers . . . . . . . 161Previously discovered blade server does notshow associated IP address . . . . . . . . 162Switch access state remains Partial Access afteraccess request . . . . . . . . . . . . 162The server reports that "Power off and Restart"was successful, but it was not . . . . . . . 164The System Identification menu options are notavailable . . . . . . . . . . . . . . 164Two different managed operating systems havethe same UUID after moving a blade systemboard to a different blade slot . . . . . . . 165Service processor is unresponsive. . . . . . 166

Network management troubleshooting . . . . . 168

Cannot view configuration of some switches 168Cannot view network interface cards . . . . 169Clicking pie chart on Network Managementsummary page may not display correct view . . 169IBM Systems Director Server sends unwanted orunexpected multicast packets . . . . . . . 170Delay in threshold page reflecting exceededthreshold . . . . . . . . . . . . . . 171Duplicate network monitor thresholds . . . . 171Offline network interface card reports incorrectstatus . . . . . . . . . . . . . . . 171

IBM Power Systems management . . . . . . 172Using IBM i resources with an IBM SystemsDirector Server . . . . . . . . . . . . 172

Remote access troubleshooting . . . . . . . 174File Management does not display files withChinese characters in the file name if these fileswere transferred with a tool other than IBMSystems Director File Management . . . . . 174File Management does not support certaincharacters in file names when using the renamefunction . . . . . . . . . . . . . . 174Remote command line prompt on a Windows2003 Common Agent managed system does nothave working scroll bars . . . . . . . . 175Unable to export file using Microsoft InternetExplorer 9 . . . . . . . . . . . . . 175

System z management . . . . . . . . . . 176Discovery of z/VM managed resources does notfunction correctly . . . . . . . . . . . 176Incorrect values are displayed for CPUUtilization and Process Count on Linux onSystem z . . . . . . . . . . . . . . 179Job status for inventory collection on IBM z/VMManageability Access Point Agent is Completewith Errors . . . . . . . . . . . . . 180

Storage systems management troubleshooting . . 180Cannot start an IBM DS Storage Manager withversion later than 10.6.x.x . . . . . . . . 180Cannot start DS storage manager when usingWindows Internet Explorer 8 . . . . . . . 181Cannot access PlatformAgentSubagent SMI-S forIBM SAS RAID Controller Module . . . . . 181DS 3000/4000/5000 proxy providerconfiguration causes provider to fail. . . . . 182Unable to discover an SMI-S provider . . . . 182After requesting access to an SMI-S provider, nostorage systems or switches are displayed . . . 183SMI-S provider configuration fails to add astorage device . . . . . . . . . . . . 183SMI-S provider configuration fails to remove astorage device . . . . . . . . . . . . 184Installing the SMI-S provider for the IBMBladeCenter S SAS RAID Controller Module onadditional systems completes with errors . . . 185Storage events not being displayed in the eventlog . . . . . . . . . . . . . . . . 185Unable to display a topology map of a SAN . . 186The SAN configuration profile is not updatedwhen a blade is changed in an IBM BladeCentersystem . . . . . . . . . . . . . . 186

vi IBM Systems Director Troubleshooting and Support Guide

Replace and remap task fails with an IBMBladeCenter S SAS RAID Controller Module fora blade whose host name is more than twelvecharacters in length . . . . . . . . . . 187iSCSI configuration accepts incomplete IPv4format addresses . . . . . . . . . . . 187Deploy of a SAS Zone configuration failed onan IBM BladeCenter after access to theAdvanced Management Module . . . . . . 188No predefined SAS zone configuration whenthere is only one SAS switch, and it is on I/OModule 4 on an IBM BladeCenter S system . . 188Mismatched configuration of two SAS switcheson an IBM BladeCenter S system . . . . . . 189Cannot view available storages when creating alogical volume in offline mode . . . . . . 189Cannot get some properties of storage devices 190SAS Port panel launched from SAS switch is notcorrect. . . . . . . . . . . . . . . 190IBM BladeCenter S SAS RAID ControllerModule menu tasks are not displayed for anattached storage array (storage subsystem) . . 191IBM BladeCenter S SAS RAID ControllerModule menu tasks fail for an attached storagearray (storage subsystem) . . . . . . . . 191A previously supported IBM BladeCenter S SASRAID Controller Module is no longer supportedafter installing IBM Systems Director 6.1.1. . . 192Cannot create RAID 0 level pools on certain LSIIRC devices . . . . . . . . . . . . . 192Capacity information is not correct for storagedevices . . . . . . . . . . . . . . 192When managing an Integrated RAID Controller(IRC), incorrect controller device information isdisplayed. . . . . . . . . . . . . . 193Some menu options are missing for anIntegrated RAID Controller (IRC) device . . . 193Some ServeRAID MR controller devices notsupported by IBM Systems Director 6.1.1 . . . 193Remote Supervisor Adaptor and RemoteSupervisor Adaptor-II devices not supported byIBM Systems Director 6.1.1 . . . . . . . . 194Storage panel or Long Running Tasks panel failswhen managing ServeRAIDMR Controller orIntegrated RAID Controller (IRC) devices . . . 195A pool with a RAID level of RAID10 on aServeRAID MR Controller device can have amaximum of four drives. . . . . . . . . 195Using tasks available on Storage panel forIntegrated RAID Controller (IRC) devices resultsin errors . . . . . . . . . . . . . . 195Controller error when starting a task . . . . 196

System status and health troubleshooting . . . . 197LPAR life-cycle indications are missing . . . . 197Automation command does not show theinteractive program window . . . . . . . 197Cannot add selected resources to a monitorview . . . . . . . . . . . . . . . 198Disk monitors does not display all folders underroot path . . . . . . . . . . . . . . 198

Error is encountered while loading sharedlibraries . . . . . . . . . . . . . . 199Power Systems server IVM events appear in theevent log with incomplete Event Text andSource fields . . . . . . . . . . . . 199Events are not created immediately when athreshold is exceeded. . . . . . . . . . 199Incorrect events reported for NICs that have ateaming configuration of active-standby . . . 200Monitored memory values are too high . . . 201Monitored disk space values are too low . . . 201Monitoring tasks are not displayed in theActions menu . . . . . . . . . . . . 201Monitors are not listed for the selected resource 202No data available error for AIX and VIOSmonitors . . . . . . . . . . . . . . 202Predictive Failure Analysis events not reportedfor System x3755 M3 servers . . . . . . . 203Resource is not returned by the browse function 204Resources are encountering problems that youneed to monitor and manage . . . . . . . 204Save changes confirmation window is invokeddespite no changes . . . . . . . . . . 204Two microprocessor monitor resources aredisplayed when only one microprocessor exists . 205

Update manager troubleshooting . . . . . . . 205Unable to import updates from networkmounted directories . . . . . . . . . . 205Getting Started wizard for update managerindicates that some systems are not supported . 206A system cannot be chosen from the GettingStarted, Install, or Install staging wizards . . . 206Error occurred trying to start the TFTP serverused for IBM BladeCenter and System xupdates . . . . . . . . . . . . . . 207Compliance is not accurate for a system . . . 207Unable to find update compliance task logs . . 208Compliance status is not accurate for IBMBladeCenter I/O modules . . . . . . . . 208Update compliance is not refreshed whenadding a nested group to a compliance policy . 209Compliance issues not resolved after successfulinstall of updates . . . . . . . . . . . 209Update compliance issue remains unresolvedafter installing IBM Director Agent 5.20.xupdates on Linux systems . . . . . . . . 210Running out disk space during updatedownload can cause random application errorsand server startup errors . . . . . . . . 210Download of updates fails due to proxy serverconnection issues . . . . . . . . . . . 211Download of updates fails with an error ofdownload size exceeded. . . . . . . . . 212Install and Installation staging tasks notavailable for an update . . . . . . . . . 212IBM BladeCenter Install and Installation Stagingtasks fail when using an FTP or TFTP server . . 213Installing out-of-band updates for IBMBladeCenter devices using SNMP fails . . . . 213Installing out-of-band updates for IBMBladeCenter devices using Telnet fails . . . . 214

Contents vii

Installing an update takes too much time . . . 215Install fails when using system groups orupdate groups . . . . . . . . . . . . 216Updates from an update group have not beeninstalled . . . . . . . . . . . . . . 216Path length is limited to 64 characters whenupdating IBM BladeCenter Out of Bandcomponents . . . . . . . . . . . . . 217Staging of updates to TFTP server can fail onextremely slow networks . . . . . . . . 217Updating IBM Director Agent version 5.20.1 onoperating systems other than Windows fails . . 218AIX upgrades that skip a Technology Level maynot report correct new level . . . . . . . 219Best practices for working with updates for IBMi . . . . . . . . . . . . . . . . . 219Uninstall fails because a restart of an IBM isystem is required . . . . . . . . . . . 220Show installed updates and Show and installupdates tasks do not display all updates . . . 221

Commands troubleshooting . . . . . . . . 222Help and error messages for the smclicommand display only in English . . . . . 222Unable to display man pages on SUSE LinuxEnterprise Server 9.x . . . . . . . . . . 222Unable to run a specific smcli command . . . 222Unable to run smcli commands from a directoryother than install_root/bin . . . . . . . . 223

Unable to run a dircli command . . . . . . 223Unable to change the language (locale) . . . . 224Unable to use double-byte character setlanguages in AIX . . . . . . . . . . . 224Output is empty for system and inventorycommands . . . . . . . . . . . . . 225Unable to connect to the CLI daemon . . . . 225Storage commands troubleshooting . . . . . 226Update commands troubleshooting . . . . . 229

Console logging and tracing . . . . . . . . 230Sensor logs and debugging . . . . . . . . . 231

Activating a log file using a configuration file 231Activating logging by creating an empty log file 232Sensor logs for debugging . . . . . . . . 233

Getting help and support . . . . . . . . . 234Finding information about IBM SystemsDirector problems . . . . . . . . . . . 234Information to provide to the IBM TechnicalSupport Center . . . . . . . . . . . . 236Getting fixes. . . . . . . . . . . . . 237Service and support information . . . . . . 237

Messages . . . . . . . . . . . . . . . 238

Notices . . . . . . . . . . . . . . 239Trademarks . . . . . . . . . . . . . . 241

viii IBM Systems Director Troubleshooting and Support Guide

About this publication

This publication provides information about specific IBM® Systems Directorproblems and how to solve them. This book also provides strategies fortroubleshooting 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 avoidinconvenient 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 damagecan occur.

Publications and related informationYou can view the same content in the IBM Systems Director Information Center asPDF documents. To view a PDF file, you need Adobe Acrobat Reader, which canbe downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.

Information centers and topic collectionsv IBM Systems

http://publib.boulder.ibm.com/eserver/View the IBM Systems information center landing page, which providesintegrated information for multiple IBM Systems products.

v IBM Systems Directorpublib.boulder.ibm.com/infocenter/director/pubs/index.jspUpdated periodically, the IBM Systems Director topic collection contains themost up-to-date documentation available for IBM Systems Director.

v IBM Systems Director plug-inshttp://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/extensionparent.htmlView the IBM Systems information center for information about how to installand 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.htmlRead the IBM Systems Director Upward Integration Modules (UIM) topiccollection to learn about how to install and use upward integration modules andmanagement packs that enable non-IBM workgroup and enterprise-managementproducts to interpret and display data that is provided by Common Agent andPlatform Agent.

v IBM Systems Director Software Development kithttp://publib.boulder.ibm.com/infocenter/director/devsdk/index.jsp

© Copyright IBM Corp. 1999, 2012 ix

View the license information regarding use of IBM Systems Director APIs andtheir associated documentation. Fill out the form to request API access. Afteryour information is reviewed, you will be contacted with additional informationregarding access to and use of the APIs.

Publications

Release Notes® 6.3.1Provides an easy reference to planning, install and troubleshootinginformation for IBM Systems Director.

IBM Systems Director Planning GuideProvides planning information, including hardware requirements forrunning IBM Systems Director components, supported IBM SystemsDirector hardware, operating systems, databases, and workgroup andenterprise systems-management software.

PDF files for installing IBM Systems Director ServerProvides detailed instructions to prepare for, install, and configure the IBMSystems Director Server.

PDF files for installing IBM Systems Director agentsProvides detailed instructions to prepare for and install IBM SystemsDirector agents on your managed systems, as well as, prepare for agentlessmanaged systems.

PDF files for upgrading and migrating IBM Systems Director ServerProvides detailed instructions to upgrade and migrate the IBM SystemsDirector Server.

PDF files for upgrading and migrating IBM Systems Director agentsProvides detailed instructions to upgrade and migrate IBM SystemsDirector agents.

Systems Management GuideProvides detailed instructions for using the Web interface and managingsystems and resources in your environment.

Troubleshooting GuideProvides information about problems and how to solve them, andstrategies for troubleshooting common problems.

Events ReferenceProvides information about IBM Systems Director events, including theevent type, description, severity, and extended details.

Commands ReferenceProvides detailed information about the systems managementcommand-line interface (smcli) commands, and other commands that canbe run directly from the command line, including configuring the database,and starting and stopping IBM Systems Director.

Hardware Command Line User's GuideProvides information about installing and using the Hardware CommandLine (formerly known as the IBM Management Processor Command-LineInterface). Command output in this release might vary from commandoutput in previous releases.

White papers and briefsv IBM Systems Director

x IBM Systems Director Troubleshooting and Support Guide

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/XBW03006USEN.PDFThis paper provides a detailed overview of the changes in IBM Systems DirectorV6.1, including the new Web interface, security features, operating systemagents, integrated plug-ins and additional plug-ins that can be separatelyinstalled.

v Value Proposition for IBM Systems Director

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/XBW03007USEN.PDFThis paper describes the challenges of operational management for enterpriseserver installations and the value provided IBM Systems Director.

v Performance Tuning and Scaling Guide for IBM Systems Director 6.3

Hardware requirements for running IBM Systems Director ServerProvides information about how to plan, implement, configure, and use an IBMSystems Director Server to manage a large configuration with optimalperformance. The Performance Tuning and Scaling Guide also containsinformation 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

IBM Redbooks® publications

www.ibm.com/redbooks/

You can also search this Web page for documents that focus on IBM SystemsDirector and specific IBM hardware; such documents often containsystems-management material. The following book is available for IBM SystemsDirector V6.1:

Implementing IBM Systems Director 6.1

Tip: Be sure to note the date of publication and to determine the version of IBMSystems Director software to which the Redbooks publication refers.

Further information

Also see the following resources for further information about IBM SystemsDirector: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 “IBM Systems Director” inthe Search field and click Search. You can then narrow your results by documenttype or product category, or use additional search terms.

v For white papers, technotes, tips, and other documents related to IBM SystemsDirector, see the Techdocs Web site at http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs.

Tip: To locate the information that you need, either select the categories that youwant to search or select UNMARKED to search all categories. Then enter “IBMSystems Director” in the for: field and click Search.

About this publication xi

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 resourcesListed here are the Web sites and information center topics that relate to IBMSystems Director.

Web sitesv IBM Systems Director

www.ibm.com/systems/management/director/View the IBM Systems Director Web site on ibm.com® which provides links todownloads and documentation for all currently supported versions of IBMSystems Director.

v IBM Systems Director Downloadswww.ibm.com/systems/management/director/downloads/View the IBM Systems Director Downloads Web site on ibm.com which provideslinks to download code IBM Systems Director, IBM Systems Director plug-ins,and IBM Systems Director upward integration modules.

v IBM Systems Director Documentation and Resourceswww.ibm.com/systems/management/director/resources/View the IBM Systems Director Documentation and Resources Web site onibm.com which provides links to product documentation, redbooks, redpapers,white papers, and learning modules related to IBM Systems Director, IBMSystems Director plug-ins, and IBM Systems Director upward integrationmodules.

v IBM Systems Director Upward Integrationwww.ibm.com/systems/software/director/downloads/integration.htmlView the IBM Systems Director Upward Integration Web site on ibm.com whichprovides more information about IBM Systems Director upward integrationmodules created by IBM and other companies. IBM Systems Director UIMsenable third-party workgroup and enterprise systems-management products tointerpret and display data that is provided by IBM Systems Director PlatformAgent managed system.

v IBM Systems Director Best Practices Wikiwww.ibm.com/developerworks/wikis/display/WikiPtype/IBM+Systems+Director+Best+Practices+WikiView updated documentation and best practices for IBM Systems Director onvarious systems.

v IBM Serverswww.ibm.com/servers/View the IBM Servers Web site to learn about IBM Systems server and storageproducts.

v IBM ServerProven®

www.ibm.com/servers/eserver/serverproven/compat/us/View the IBM ServerProven Web site to learn about hardware compatibility ofIBM System x® and BladeCenter® systems with IBM applications andmiddleware, including IBM Systems Director.

xii IBM Systems Director Troubleshooting and Support Guide

Forumsv IBM Systems Director Forum (System x, System z®, Power Systems™)

www.ibm.com/developerworks/forums/forum.jspa?forumID=759View the IBM Systems Director Forum Web site on ibm.com to discussproduct-related issues pertaining to IBM Systems Director, IBM Systems DirectorUIMs, and IBM Systems Director extensions. This Web site includes a link forobtaining the forum using a Rich Site Summary (RSS) feed.

v IBM Systems Director 6.x SDK Forumwww.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0View the IBM Systems Director 6.x SDK Forum Web site to discuss issuespertaining to the IBM Systems Director Software Development Kit (SDK). ThisWeb site includes a link for obtaining the forum using a Rich Site Summary(RSS) feed.

v IBM Systems Forumswww.ibm.com/developerworks/forums/dw_esforums.jspView the IBM Systems Forums Web site on ibm.com to learn about variousforums that are available to discuss technology-related and product-relatedissues pertaining to IBM Systems hardware and software products. This Web siteincludes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

How to send your commentsYour feedback is important in helping to provide the most accurate and highestquality information.

If you have any comments about this book or any other IBM Systems Directorpublication, go to the IBM Systems Director information center Web site atpublib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will findthe feedback page where you can enter and submit comments.

About this publication xiii

xiv IBM Systems Director Troubleshooting and Support Guide

Troubleshooting and support

Use this section to troubleshoot and resolve problems with IBM Systems Director6.2 or later. To troubleshoot problems that are specific to earlier versions of IBMSystems Director, see the documentation for that version.

If you run into a problem that is not covered in this documentation, check any ofthe following resources for further information about troubleshooting IBM SystemsDirector: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 “IBM Systems Director” inthe Search field and click Search. You can then narrow your results by documenttype or product category, or use additional search terms.

v For white papers, technotes, tips, and other documents related to IBM SystemsDirector, see the Techdocs Web site at http://www.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs.

Tip: To locate the information that you need, either select the categories that youwant to search or select UNMARKED to search all categories. Then enter “IBMSystems 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 workaroundsThe following topics describe limitations and workarounds for IBM SystemsDirector.

Discovery profile auto-unlock and auto-inventory notsupported for IBM Director Agent

This problem affects users when using a discovery profile to discover IBM DirectorAgents.

Problem

When using a discovery profile to discover IBM Director Agents, automaticallyrequesting access and automatically collecting inventory are not supported.

Note: In the Discovery Profile wizard, the protocol for discovering IBM DirectorAgents is called IBM Systems Director 5.x Common Agent Discovery. The defaultprofile that discovers IBM Director Agents is called Default Common AgentDiscovery.This limitation is restricted only to IBM Director Agents supported on IBMDirector 5.10 and its update versions and IBM Director 5.20 and its updateversions. It does not apply to Platform Agents. When discovering a combination of

© Copyright IBM Corp. 1999, 2012 1

agent types with the same profile, other agents that are discovered (not IBMDirector Agents) support automatically requesting access and automaticallycollecting inventory.

Resolution

This is a current limitation of IBM Systems Director 6.x.

Agent installation does not generate eventsThis problem affects installation of all agent packages on managed systems usingthe Agent Installation Wizard.

Problem

When you attempt to install an agent package on a managed system, no events aregenerated or logged.

Resolution

This is a current limitation of IBM Systems Director 6.1.

BladeCenter is offline after the AMM failed overThe BladeCenter chassis appears as “offline” after the AMM fails over.

Problem

When the AMM fails over, the BladeCenter chassis appears as “offline” in IBMSystems Director.

Cause

When Advanced Failover is configured on the Advanced Management Module(AMM), the Swap Management Module IP Addresses option must be selected. Ifthis option is not set correctly, IBM Systems Director sees the BladeCenter chassisas “offline” when the AMM fails over.

Resolution

Select the Swap Management Module IP Addresses option.

Changes to the network interface card (NIC) configurationcannot be deployed to operating system resources

This problem affects the Network Configuration template when applied tooperating system resources.

Problem

When you try to modify the IP address, gateway, and subnet mask of the networkinterface card (NIC) that is currently used to interconnect on this template at thesame time and want to deploy this change to the operating system resource, thistask fails.

2 IBM Systems Director Troubleshooting and Support Guide

Explanation

This is a limitation of IBM Systems Director 6.1. The Platform Agent and CommonAgent cannot support modification of the IP address, gateway, and subnet mask ofthe network interface card (NIC) used to interconnect.

Command fails on smcliThis problem affects systems running some language-specific versions of MicrosoftWindows, such as Korean and Japanese versions.

Problem

When you run a command that includes a backslash (\) on the IBM SystemsDirector command-line interface (smcli), the command fails to run.

IBM Systems Director command-line interface (smcli) and virtualization managercommands use the backslash (\) for various commands. For example, thebackslash is used when designating the full path name to a virtual serverconfiguration file. However, some language-specific versions of Microsoft Windowsuse a different character for backslash. Therefore, when a backslash is used withsmcli, it fails to run on that language-specific version of Microsoft Windows. Forexample, this problem occurs with the Korean and Japanese versions of Windows.

Resolution

No action is suggested. This problem is a known limitation.

Common Agent and Platform Agent are not automaticallydiscovered after installation

This problem affects the installation and discovery of Common Agent and PlatformAgent.

Problem

The installation of Common Agent or the installation of Platform Agent reportscompletion, but the installed agent has not been discovered by IBM SystemsDirector Server.

Resolution

After the installation of Common Agent or the installation of Platform Agentreports completion, wait a moment for IBM Systems Director Server toautomatically discover the installed agent. If after 5 minutes, IBM Systems DirectorServer does not automatically discover the installed agent, manually discover theinstalled agent. For instructions, see Performing a system discovery.

Date and time remain editable after deselecting the Power OnServer

This limitation applies to the power configuration template for RSA.

Troubleshooting and support 3

Problem

When creating a power configuration template for RSA, if you deselect Power OnServer, the date and time under Power On Server will be greyed out, but willremain editable.

Delete operations take a long time to completeThis problem affects the responsiveness of IBM Systems Director Server.

Problem

When deleting a managed resource or any other resource from IBM SystemsDirector Server, the resource might be removed from the IBM Systems DirectorWeb interface promptly, but IBM Systems Director Server might seem slowafterwards.

Similar behavior might be exhibited when running the cleanupd command.

Investigation

A managed resource might have many other resources associated with it that mustbe removed along with managed resource. Processing is required to determinewhat other resources and relationships must be removed and this processing takestime. All of the affected resources are deleted at the same time as one transactionin the database. The database transaction might be a long-running process thatconsumes a lot of processor bandwidth. IBM Systems Director can be configured touse one of four databases: Apache Derby, IBM DB2 Universal Database™, MicrosoftSQL Server, and Oracle Database. IBM DB2 Universal Database, Microsoft SQLServer, 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 IBMSystems Director Server will return to its normal state.

Resolution

To workaround this limitation, schedule these problematic delete operations duringtimes when the least number of users will be affected.

Excessive windows prompting for undoable disk poweractions

This problem affects systems using virtualization manager subagent for VMwareVirtualCenter.

Problem

When a virtual server has one or more undoable disks and a power operationoccurs on that virtual server, VMware VirtualCenter requires user input tocomplete the operation. If the power operation is originated by IBM SystemsDirector, then IBM Systems Director provides the required input. However, if thereis a VMware Remote Console open at the time that the power operation occurs, awindow opens that asks for the required information even though it has beenprovided by IBM Systems Director. When a user attempts to provide theinformation that was requested, an error message is displayed.

4 IBM Systems Director Troubleshooting and Support Guide

Resolution

No action is suggested. This problem is a known limitation.

File Manager displays a blank tableThis problem affects Common Agent managed systems.

Problem

You are using IBM Systems Director and select System Configuration > RemoteAccess > File Management on a Common Agent or Level 2: IBM Director Agent5.20.x managed system. You navigate to a directory with more than 16,000 files init and a blank table appears after a few minutes.

Explanation

When using Common Agent or Level 2: IBM Director Agent version 5.20, thenumber of files under a directory that File Manager can return is less than 16,000files. If the number of files under a directory is more than 16,000 the File Managertable appears blank.

Resolution

If you are using Common Agent or Level 2: IBM Director Agent version 5.20, onlyselect directories with less than 16,000 files in File Management.

File Manager fails to copy files larger than 1.5 GBThis problem affects Microsoft Windows managed systems.

Problem

You are using IBM Systems Director to discover a Windows managed system andhave gained full access to the target system. You right-click the operating systemfor the target system and select System Configuration > Remote Access > FileManagement. Then you upload a file greater than 1.5 GB. The upload commandfails.

Explanation

This problem is related to the available memory on the server. File Manager needsa server to have a large amount of available memory to load a big file. If the serverdoes 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 otherapplications to increase the amount of available memory.

Help selection is a question markThis problem affects the IBM Systems Director Web interface in Italian only.

Troubleshooting and support 5

Problem

For Web browsers that are set to Italian, the Help selection provided in the upperright corner of the IBM Systems Director Web interface is represented by aquestion mark (?).

Resolution

IBM Storage Configuration Manager (SCM) 2.10 or earlier doesnot support non-English operating systems

This problem affects users of IBM Storage Configuration Manager version 2.10 orearlier.

Problem

IBM Storage Configuration Manager (SCM) version 2.10 or earlier does not haveNational Language Support built-in. As a result, it is not supported to run onnon-English operating systems.

Resolution

This is a current limitation of IBM Storage Configuration Manager 2.10 or earlierversions.

Limitations using IBM Systems Director to manage resourcesbehind a NAT firewall

This problem affects users who attempt to use IBM Systems Director to manageany one of several types of resources that is located behind a network addresstranslation (NAT) firewall.

Problem

IBM Systems Director cannot manage the following adapters and modules whenthey are located behind a NAT firewall:v Remote Supervisor Adapterv Remote Supervisor Adapter IIv Integrated Management Module IIv Management Module

Also, a few other types of resources that are located behind a NAT firewall mightbe unable to reliably send events to the management server.

Explanation

The following limitations affect IBM Systems Director when attempting to manageresources that is located behind a NAT firewall:v The following types of adapters and modules cannot reliably respond to SLP

requests received from Systems Director:– Remote Supervisor Adapter– Remote Supervisor Adapter II– Integrated Management Module II– Management Module

6 IBM Systems Director Troubleshooting and Support Guide

The device receives the SLP request on port 427 but sends a response on arandom port number, which NAT does not support. This inability to reliablycommunicate with the management server prevents Systems Director fromdiscovering the device.

v When located behind a NAT firewall, a few types of resources cannot reliablysend events to the management server. Resources that are negatively affected bybeing located behind the NAT firewall include:– APlatform Agent managed system– An Advanced Management Module– AHardware Management Console

Important: Systems Director can successfully discover and manage a properlyconfigured Common Agent managed systems. For more information aboutconfiguring a Common Agent managed system, see the Common Agentinstallation 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 devicesThe capacity information displayed on the Local Storage row of the StorageManagement 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 0because of this limitation. The other rows (Network storage and IBM BladeCenterstorage) are correct.

Resolution

Use operating system utilities or storage management applications to determineusable and available storage capacity.

Table view entries do not include Linux operating systemversion information

This problem affects Common Agent managed systems and Platform Agentmanaged systems that run the Linux operating system.

Problem

After discovering and requesting access to Common Agent managed systems orPlatform Agent managed systems that run the Linux operating system, discoveryresults and other table views do not display the Linux version information forthese systems. Affected table views include the discovery results (the DiscoveredManageable Systems table) and the tables displayed by using the ResourceExplorer task.

Troubleshooting and support 7

Resolution

To resolve this problem, collect inventory for the affected systems. After collectinginventory, table view entries for the affected systems include the Linux operatingsystem version information.

Event Filter Builder tree displays multiple Windows event lognodes

This problem affects the Event Filter Builder tree in the advanced event filter pathof the Event Automation Plan wizard.

Problem

In the Event Filter Builder window (a Launched task provided for advanced eventfilter creation), on the Event Type page, when you clear the Any check box, twoselection nodes are displayed for Windows Event Log events:v CIM > Windows NT Event Logv Windows Event Log

Resolution

IBM Systems Director 6.1 is working as designed. You can create an event filterwith either selection.

The OID for different SNMP traps are the sameThis problem affects the Send an SNMP trap reliably to a NetView® host eventaction.

Problem

For any event that the Send an SNMP trap reliably to a NetView host event actionredirects 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 version5.20 and earlier.

Removing a managed operating system does not remove themanaged server

This limitation affects removing a managed system from management by IBMSystems Director.

Problem

Managed systems are represented by two resources in IBM Systems Director: aserver resource that represents the physical server, and a system resource thatrepresents the operating system installed on the server. When you remove a systemresource, the corresponding server resource for the managed system is notremoved.

Explanation

This is a known issue with IBM Systems Director.

8 IBM Systems Director Troubleshooting and Support Guide

Resolutionv After removing the system resource, also remove the corresponding server

resource.

Limitations of large tablesThese problems exist in the table views in the IBM Systems Director Web interface.

Problem1. When you select a group that contains related resources, the resources are

normally displayed as nested resources in a table. However, when the groupcontains a large number of discovered resources, you notice that the resourcesare not displayed in a nested view. For example, you might see a list of virtualservers 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 thenumber 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 searchand filtering. Columns that cannot be filtered will not have a filter link whenthe filter row is displayed. Columns that cannot be filtered will also notsupport the search function. For example, searching on the contents of the IPAddresses or IP Hosts columns in large tables does not work.

Explanation

These problems can occur when the total number of resources and relationships ina group exceeds 1,000. These problems are a known limitation of the table view.

Selections or data entered into fields is lostThis problem affects any IBM Systems Director pages and windows that containlists, 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 whichoverlays the first page, and then return to the first page, the selections and datathat 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 currentrelease.

The Severity column always reports InformationThis problem affects the Hardware Log task when used on a resource that containsan IPMI Baseboard Management Controller (BMC) service processor.

Troubleshooting and support 9

Problem

When viewing hardware log entries retrieved from a BMC service processor, theseverity is always reported as Information.

Explanation

This is a limitation of the BMC service processor. Log entries in the BMC serviceprocessor do not contain severity information. The Hardware Log task displaysInformation as a default value.

Warning message recorded after installing the SMbus or LM78device 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 tothe 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.

Explanation

This warning message is generated if the Red Hat Enterprise Linux kernel wascompiled with versioned symbols enabled. Ignore this message; the device driverloaded and will operate correctly.

Switch does not respond to IP address change(IBM Systems Director 6.1 only) This problem affects IBM BladeCenter switchesthat are not discovered by way of the BladeCenter chassis. This problem isresolved in IBM Systems Director version 6.1.1.

Problem

When a switch is directly discovered and not discovered through the BladeCenterchassis, 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 IPaddress, a second switch managed resource is created. The first managed resourcedisplays 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 wheresystem_name is the unique ID or name of thesystem.

10 IBM Systems Director Troubleshooting and Support Guide

In the IBM Systems Director Web interface Right-click the switch and click Remove.

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

Brocade Fibre Channel switch has unexpected status ofOffline

This limitation occurs when multiple management servers manage a single BrocadeSMI Agent 120.11.0 or a single Brocade Network Advisor (BNA).

Problem

When multiple management servers manage one Brocade SMI Agent 120.11.0 orBNA, the switches managed by the SMI Agent or the BNA might get into anOffline state.

Explanation

This issue is caused by the maximum limit of Common Information Model (CIM)connections supported by a single SMI Agent 120.11.0 or BNA. Brocade states thatboth the Agent and BNA support up to 10 CIM connections.

Resolution

To avoid this issue, limit the number of management servers deployed to managethe same SMI Agent or BNA:v If both a Storage Control Farm path and an SMI-S path are used simultaneously

to manage the agent, using a single management server is supported to managethe SMI Agent or BNA

v If only one path is used, either a Storage Control Farm path or an SMI-S path,using a maximum of two management servers is supported to manage the SMIAgent or BNA

Another method that avoids this issue is to manage the switches by using severalSMI Agents or BNAs instead of one.

Switch information is not accurate in IBM Systems DirectorServer

Switch alerts are not reflected on the switch resource in the IBM Systems DirectorServer.

Problem

Telnet to the switch from a command line session and issue some commands suchas switchDisable or portDisable. The state change is not reflected on the switchresource in IBM Systems Director Server. The access state of the switch remainsunlocked.

The command switchDisable will cause all Fiber Channel ports to be offline, butthe user can still configure the switch. The switch itself is still online and can beconfigured.

Troubleshooting and support 11

IBM Systems Director Server might fail to start in IPV6-onlyenvironment on Linux platform

This problem affects the IBM Systems Director Server when configured forIPv6-only after being installed on a Linux system.

Problem

After IBM Systems Director Server is installed on a Linux system that has (or ischanged to) an IPV6 network configuration, one of the following problems mightoccur:v After a significant time, the server does not startv After starting, which might take a significant time, IBM Systems Director does

not function correctly. For example, the IBM Systems Director Web interfacemight be unavailable.

When IBM Systems Director is installed on a system with an IPv4 networkconfiguration, you might re-configure the system to have an IPv6-onlyenvironment. After re-configuring the environment as IPv6 and restarting theserver, 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 usesthe following configuration settings before you install IBM Systems Director Serveror 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 thehost name is server.abc.com, the contents of /etc/hosts might look like thefollowing example:

::1 localhost, localhost.localdomain2002:1234:5678::1 server.abc.com# 10.12.34.56 server.abc.com

Note: Comment out or remove the original IPv4 addresses, with the followingexception: 127.0.0.1. Even when configured as IPv6-only, the 127.0.0.1 IPv4loopback address is still reachable, so using 127.0.0.1 is optional. Some Linuxdistributions use a default value of localhost6 for the ::1 IPv6 loopback address,which is different from localhost for an IPv4 configuration. In this case, keep127.0.0.1 as the localhost value.

4. Configure a reachable DNS server with IPv6 address in the /etc/resolv.conffile. This entry is used for IBM Systems Director Server and Common Agent toresolve 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 IBM Systems Director Troubleshooting and Support Guide

v If the DNS server returns an IPv4 address for a host name, the IPv6-onlyIBM Systems Director Server or Common Agent is unable to connect to theIPv4 address.

A possible workaround for this issue is to add the same entries from the DNSserver to the /etc/hosts file so that they resolve to IPv6 addresses. The Linuxsystem first uses the /etc/hosts file, then uses the DNS server. Having IPv6entries in the /etc/hosts file ensures that the host names resolve to correct IPv6addresses.

Tables are not displayed correctlyThis 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 DirectorWeb interface, tables displayed on the page might not be displayed correctly.

Resolution

This is a limitation of IBM Systems Director. Click on the tab again and the pagewill redraw and the tables will be displayed correctly.

The cimserver service stopsThis limitation affects Platform Agent managed systems with both Platform Agentand 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 withthe Xen kernel enabled.

Unable to filter events for virtual server failuresThis problem can affect systems that are running the virtualization managersubagent for VMware ESX Serveror 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 completesuccessfully.

v Managed Resource > Managed System Resource > Logical Resource > System >Computer System > Server > Lifecycle > The command did not completesuccessfully.

Troubleshooting and support 13

v Managed Resource > Managed System Resource > Logical Resource >ServiceAccessPoint > RemoteServiceAccessPoint Service > The command did notcomplete successfully.

v Managed Resource > Managed System Resource > Logical Resource > System >Admin Domain > Farm > Lifecycle > The command did not completesuccessfully.

v Managed Resource > Settings > Resource Allocation Settings > Changes > Thecommand did not complete successfully.

The target system for the event automation plan is a system running virtualizationmanager subagent for VMware ESX Server, or VMware VirtualCenter.

A task such as a virtual server relocation or a virtual server power operation failedon one of the systems where the automation plan is applied, but the automationplan was not processed as expected.

Explanation

IBM Systems Director cannot filter the failed events for systems running VMwareESX Server, or VMware VirtualCenter. This problem is a current limitation.

Virtual farm events are not filteredThis problem can affect virtual farms in any virtualization environment

Problem

You have created an automation plan with the event filter, A virtual farm has beencreated. You have selected to apply the automation plan to the group,Virtualization Groups. A virtual farm event occurs, but the automation plan is notprocessed as expected.

Resolution

Edit the automation plan and select the target group to be All Systems, instead ofVirtualization Groups.

Virtual farm view does not refresh when hosts change(IBM Systems Director 6.1 only) This problem can affect host information in anyvirtualization 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 hostinformation is not updated dynamically in the Virtual Farms view.

Resolution

To refresh the Virtual Farms view, close the tab, and open it again. ExpandAvailability in the navigation pane, and select Virtual Farms.

14 IBM Systems Director Troubleshooting and Support Guide

Virtualization manager tasks fail to start in multi-NICenvironment

(IBM Systems Director 6.1 only) This problem affects systems that have multiple,active network interface cards (NICs) installed, as well as IBM Systems Directorvirtualization manager subagent. This problem is resolved in IBM Systems Directorversion 6.1.1.

Problem

When you attempt to start a virtualization manager task, such as Connect, the taskdoes not seem to work.

Investigation

You can check the activation logs to confirm an error.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 systemIBM 8863 1RU XxXxXxX. The IPC remote service access point does not have therequired 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 activeNICs, 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 sizefor 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 andWindows 2008.

Troubleshooting and support 15

Resolution

There is no resolution for this limitation. The correct size for the installed PlatformAgent is approximately 45MB.

Antivirus programs might conflict with certain IBM SystemsDirector processes

Certain Symantec Antivirus and McAfee program functions can conflict withcertain IBM Systems Director processes and cause problems in your environment.

Problem

Symantec Antivirus v10 Tamper Protection and McAfee On-Access Scan can slowdown or even block some IBM Systems Director processes. If your system ishaving 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.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 McAfeeOn-Access Scan May Conflict with Certain Director Processes for furtherinformation about and workarounds for these problems.

Receiving alerts associated with an LSI 1030 ControllerOnly IBM Systems Director CIM events are generated for alerts associated with anLSI 1030 controller. This issue is documented in APAR IC62863.

Problem

Alerts for issues with the LSI 1030 controller are only sent as IBM Systems DirectorCIM 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 beadded. However, IBM Systems Director can be used to forward the alerts to theneeded endpoints by creating an event action plan that receives the alert andforwards it in the proper format, such as SNMP trap or TEC event, to theappropriate end point.

Additional information

The Adaptec ServeRaid manager for the Common Agent must be installed in orderto receive CIM events associated with the LSI 1030 controller.

16 IBM Systems Director Troubleshooting and Support Guide

Incorrect version listed for Common Agent 6.2.0.1 on AIXThis 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, theCommon Agent version that is listed in /opt/ibm/director/version.key does notmatch 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.

Resolution

This problem does not have any impact on the functionality of IBM SystemsDirector, so you can ignore it.

Cannot restart the OS for managed AIX 6 CASThis problem affects AIX systems.

Problem

From the IBM Systems Director system, you run the shutdown -r +1 remotecommand to restart the AIX 6 operating system on a managed common agentservices agent. However, the command hangs when unmounting the file systemsand fails to restart the operating system.

Explanation

The remote command line does not have the appropriate file permissions tounmount 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

Platform Agent events sent over SSL are not receivedThis problem affects Platform Agent 6.3.1 on Linux and Windows.

Problem

IBM Systems Director Server does not receive Platform Agent events sent over asecured destination.

Explanation

This is a known limitation of Platform Agent 6.3.1 on Linux and Windows.

Troubleshooting and support 17

Platform Agent 6.3.1 does not support event delivery over SSL. When the PlatformAgent CIM client creates an event subscription with a secured destination, thesubscription does not properly resolve the secured destination.

A subscription is a combination of a handler and a filter, and a secured destinationis part of the handler. So, for Platform Agent, a secured destination is specifiedwith the following format:https://host_name:port/

where host_name is the IP or host name of the CIM client that will receive theevent, and port is the port through which the secured communication will travel.

So, whenever CIM clients create subscriptions using the above format, PlatformAgent is unable to deliver the event to the secured destinations.

Resolution

There is no resolution for this limitation. An available workaround is to use aunsecured destination (http) to create the subscription on Platform Agent.

Update manager limitations and workaroundsThis section describes limitations and workarounds specific to the update managerplug-in.

Compliance policies incorrectly indicate that MegaRAIDcontroller firmware needs updatingThis problem affects the update manager and Inventory tasks for Platform-Agentmanaged systems with MegaRAID controllers. The problem has been specificallyobserved 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 thatthe 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 onlyfour characters, but the MegaRAID controller firmware version levels have morethan four characters.

Resolution

Manually check the firmware version.

Update Manager does not support compliance policies for somedevicesUpdate manager supports update deployment for the specified software for somedevices, but does not support compliance policies for these devices.

18 IBM Systems Director Troubleshooting and Support Guide

Problem

Update manager supports update deployment for the specified software on thefollowing devices, but does not support compliance policies:v Intel Chipset device driverv MSI Chipset device driverv OSA device driver

Explanation

This is a limitation.

Cannot set up a compliance policy for a device that does nothave drivers installedThis limitation affects compliance policy feature of update manager.

Problem

IBM Systems Director cannot set up a compliance policy for a device on amanaged system if there are no device drivers already installed for the device.

Resolution

To enable update deployment and creation of compliance policies for devices,install drivers for the devices.

Update manager does not support update deployment orcompliance policies for some devicesUpdate manager does not support update deployment or compliance policies forthe specified software on certain devices.

Problem

Update manager does not support update deployment or compliance policies forthe specified software on the following devices:v AMD PowerNow device driverv Broadcom for IBM BladeCenter JS21v cKVM firmwarev IBM 10 GB Ethernet device driverv IBM 10 GB Ethernet network interface cardv Intel IDE MegaRAID device driverv LSI MegaRAID firmwarev Netxen 10Gb Ethernet daughter cardv Remote Supervisor Adapter II video BIOS

Explanation

This is a limitation.

Update manager cannot set up compliance policies for Adaptec8i, 8k, and 8k-l controllersThis limitation affects the update manager task for IBM Systems Director.

Troubleshooting and support 19

Problem

Attempting to set up compliance policies for Adaptec 8i, 8k, and 8k-l controllersdoes 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 IBMBladeCenter model JS21 does not raise compliance issuesThis limitation affects update manager when working with the IBM BladeCentermodel JS21.

Problem

Update manager will always show the PCI-XDDR SAS firmware for the IBMBladeCenter JS21 blade as compliant. Update manager will not alert the user thatthe firmware needs to have updates installed.

Explanation

At present, there is only one PCI-XDDR SAS firmware update available. It isunlikely that a monitored system is out of date. If needed, you can force install theupdate.

IBM i compliance displays installed PTF groups as requiredThis problem occurs when you use IBM Systems Director 6.1 to manage IBM isystems 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. Insteadyou might see a yellow status for those systems.

Explanation

IBM Director 5.20.x inventory does not contain group PTF information. Withoutthat inventory information, IBM Systems Director 6.1 will always show group PTFsas being required

When a PTF group is added to the compliance policy, compliance will show a redstatus if group PTFs are missing. If all the individual group PTFs are installed, butthe group PTF information is missing, compliance will show a yellow state. IBMDirector 5.20.x systems in yellow compliance state might be fully compliant.

This is a known limitation for IBM i updates.

20 IBM Systems Director Troubleshooting and Support Guide

Update installation task fails with error message ATKUPD826EThis problem affects users of update manager.

Problem

When using the “Update IBM Systems Director” page or the installneeded CLIcommand to import and immediately install updates, the task fails with thefollowing error message: ATKUPD826E - Updates could not be downloadedbecause they were not found at the download location.

Investigation

The job log for the update installation task or the installneeded CLI commandoutput should provide an error message with the updates that were notdownloaded. For example:ATKUPD611E The update "com.ibm.director.mgr.remote.server.feature_6.2.1" has notbeen downloaded, so it will not be staged or installed. Download the update, andattempt to perform the operation again.

Check to see if the update is listed as downloaded by running the smcli lsupd -alupdateid command. For example:c:\download\server\SysDir6_2_1>smcli lsupd -al com.ibm.director.mgr.remote.server.feature_6.2.1com.ibm.director.mgr.remote.server.feature_6.2.1:

DisplayName: IBM Systems Director remote manager server featureDescription: Provides the IBM Systems Director remote manager server fun

ctionality.Version: 6.2.1UpdateID: com.ibm.director.mgr.remote.server.feature_6.2.1Severity: MediumComponentName: IBM Systems DirectorVendor: IBM CorporationRestartType: Restart after all updates are installedSuperseded: falsePlatform: IBM Systems DirectorUninstallable: falseBuildDate: 2010-08-25T00:52:02-04:00BuildNumber: LGZU26AFixType: IndividualPackageType: baseInstallSoftwareID: SystemsDirectorCategory: ApplicationImpactStatement: AvailabilityAcquiredDate: 2010-08-27T16:11:15-04:00TotalSize: 305148Downloaded: yesFilenames: { ’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 contentcom.ibm.director.mgr.remote.server.feature_6.2.1.zip

9885 metadata downloaded deploymentDescriptorcom.ibm.director.mgr.remote.server.feature_6.2.1.dd.xml

3037 metadata downloaded packageDescriptorcom.ibm.director.mgr.remote.server.feature_6.2.1.pd.sdd

7640 metadata downloaded readMecom.ibm.director.mgr.remote.server.feature_6.2.1_readme.txt

Troubleshooting and support 21

Explanation

On faster systems, there is a rare condition that can occur when immediatelyinstalling needed updates after importing them, which is accomplished by usingthe import path from the “Update IBM Systems Director” page or the -F optionwith the installneeded command. In this situation, updates are processing in thedatabase on previously created records that represent updates. However, theinstallation code is already running on resources in memory that have not yet hadtheir property values updated. This leads to the error about an update that is notdownloaded 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 theinstallation by running smcli installneeded -v -F -I. Because the updates arealready downloaded, the installation should start and the staging step shouldcomplete successfully.

v If the value of the Downloaded property is “no”, then ensure that all of the filesare in the source import location, then run the smcli importupd command withthe -o option. After the updates are downloaded, restart the installation.

Additional information

To view the job log for the update installation task in the IBM Systems DirectorWeb interface, complete the following steps:1. Click on Resource Explorer.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.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 systemlevels are updated correctlyThis problem affects the use of update manager to update AIX.

Problem

When using update manager to install AIX updates, the installation task mightoccasionally fail with a status of “Complete with errors”. However, the AIXoperating system level is successfully updated.

Explanation

The update manager for AIX extension deems an update installation successfulwhen both of the following conditions are satisfied:v The nimclient 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 nimclient command to updateAIX. This process installs AIX file sets in the update package. If one or more file

22 IBM Systems Director Troubleshooting and Support Guide

sets are not correctly installed, the installp command fails with a nonzero returncode. Update manager then considers the task not totally successful and sets thestatus of the task to “Complete with errors”.

The result of the oslevel -s command returns the AIX operating system level. Thecommand checks only certain file sets, though, and some are overlooked. So, evenif the level of the AIX operating system appears to be updated when you use thismethod to check it, some file sets in the update package were potentially still notinstalled correctly.

Resolution

If the installp command returns a status of “Complete with errors” when youapply updates to AIX, run the oslevel -s command on the target system to see ifthe level value has changed, then take the appropriate action depending on theresults:

The level value has changedIf the level value has changed, then most likely the major updates wereapplied successfully but some packages failed to install. Packages can failto install for many reasons, including because prerequisites are missing orthe packages were not previously installed and therefore not eligible forupdate. Complete either or both of the following sets of steps to determineand solve the problem:

Check the logs

1. See the /var/adm/ras/nim.installp log file for details about thepackages that failed. The following example excerpt from thatfile shows clustering packages that were not applied becausethey were not previously installed on the operating system:cluster.hativoli.server 5.5.0.0 USR APPLY FAILEDcluster.hativoli.server 5.5.0.0 USR CLEANUP SUCCESScluster.hativoli.client 5.5.0.0 USR APPLY FAILEDcluster.es.server.rte 5.5.0.0 ROOT APPLY FAILEDcluster.es.server.rte 5.5.0.0 ROOT CLEANUP FAILED

This information is usually located at the end of the log file, oryou can search the log file for the name of the file set.

2. Take the appropriate action based on what you find in the logfile.

Check for missing file sets

1. Run the instfix -i | grep ML command to list all levels andwhether all file sets were found for each. For example, you willreceive the following output if you cannot reach level 6100-06:#instfix -i | grep ML

All filesets for 6100-00_AIX_ML were found.All filesets for 6100-01_AIX_ML were found.All filesets for 6100-02_AIX_ML were found.All filesets for 6100-03_AIX_ML were found.All filesets for 6100-04_AIX_ML were found.All filesets for 6100-05_AIX_ML were found.Not all filesets for 6100-06_AIX_ML were found.

2. Run the oslevel -rl level_ID command, where level_ID isthe ID of the level for which not all file sets were found, to listthe missing file sets for that level. For example, you will receivethe following output it you run the command to determinewhich file sets are missing from level 6100-06:

Troubleshooting and support 23

#oslevel -rl 6100-06Fileset Actual Level Recommended ML------------------------------------------------------Java6.sdk 6.0.0.200 6.0.0.215

In this example, Java6.sdk version 6.0.0.215 was missed, so theoperating system cannot reach level 6100-06 and it remains at6100-06-05-1115.

3. Update manager failed to install whichever file set is listed, soyou need to install it manually. Go to Fix Central and enter inall the applicable information for your missing file set todetermine which .bff file contains the missing file set. Forexample, to manually install Java6.sdk, select “AIX” for theproduct group, “6.1” for the version, and “Fix search” for thefix type. Enter “Java 6 sdk” in the search field and select“Fileset information” as the document type. Follow the link thatis provided to find that the individual fix is U831435(U831435.bff).

4. Run the following command on the NIM master to find theneeded .bff file:# find /export/um_lpp_source/ -name fix_name.bff/export/um_lpp_source/path1_to_fix/fix_name.bff/export/um_lpp_source/path2_to_fix/fix_name.bff

where fix_name is the fix name that you previously determined,and the path_to_fix values are version directories in which thefix potentially resides.

5. Copy the .bff file to the managed server.6. On the managed server, run the following command to

manually install the fix:# installp -acgN -d fix_name.bff all

7. Run oslevel -s again to confirm that the operating systemlevel is now listed correctly.

8. Using IBM Systems Director Server, collect inventory on themanaged server, check for updates, and retry the installation ofthe desired AIX level. The task should complete without errors,and the managed server should possess the expected operatingsystem level.

The level value has not changedIf 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.

Related information:

Fix Central

Installation and migration troubleshootingThis section provides information about problems and workarounds related toinstalling, uninstalling, and migrating IBM Systems Director.

24 IBM Systems Director Troubleshooting and Support Guide

AIX installation troubleshootingThis section provides information for specific problems and workaroundsassociated with AIX installation.

Review all troubleshooting topics for possible solutions. For additionaltroubleshooting information, see the IBM Systems Director Release Notes.

Applications require a different openssl file set versionThis 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. Thefollowing error message is a typical one you will see when this problem occurs:# sshexec(): 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 installthe installp version of the openssl file set. This might cause problems withapplications 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. Theopenssl installp file set installs libraries into /usr/lib and the openssl rpm file setinstalls 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;

Linux installation troubleshootingThis section provides information for specific problems and workaroundsassociated with Linux installation.

Review all troubleshooting topics for possible solutions. For additionaltroubleshooting information, see the IBM Systems Director Release Notes.

Error message indicates a supported Linux distribution couldnot be detectedThis 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:

Troubleshooting and support 25

– 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 Linuxdistribution that is not supported by the following RPMs:v IBMCimCorev IBMCimExtv DirectorCimCorev xSeriesCoreServices-level1v dsav lsi_ir_hhrv pSeriesCoreServices-level1

Resolution

To correct the problem, install a supported Linux distribution. See the IBM SystemsDirector Planning, Installation, and Configuration Guide for your system.

SELinux is set to enforce security policiesThis problem affects only systems running Linux.

Problem

You are having trouble installing IBM Systems Director Common Agent becauseSELinux is in the enforcing state.

Explanation

If your server runs Red Hat Enterprise Linux version 4 or 5, SELinux might beenabled and enforcing security policies on your system. IBM Systems DirectorCommon Agent might have trouble if SELINUX is set to enforcing.

Resolution

You must ensure that SELinux is set to permissive before you install IBM SystemsDirector 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 VMwaremanaged systems using the Agent Installation WizardThis problem affects using the Agent Installation Wizard to deploy agents onmanaged systems running Red Hat Enterprise Linux or VMware ESX.

26 IBM Systems Director Troubleshooting and Support Guide

Problem:

Attempts to install agents on Red Hat Enterprise Linux or VMware managedsystems 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: com.jcraft.jsch.JSchException: Algorithm negotiation fail

at com.jcraft.jsch.Session.receive_kexinit(Session.java:555)at com.jcraft.jsch.Session.connect(Session.java:334)at com.jcraft.jsch.Session.connect(Session.java:190)at 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 changingthe configuration of the SSH daemon on the VMware system.

Resolution:

Perform the following steps to ensure that agents can be installed on managedsystems running Red Hat Enterprise Linux or VMware ESX using the AgentInstallation 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

6. Use VMware vSphere Client Security Profile Properties to enable ibmsa andibmcim.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.

7. Ensure the validity of any stored public key data for the target system inroot_SSH_data_directory/known_hosts on IBM Systems Director Server. See“Common Agent cannot be installed on an AIX or Linux system” for moreinformation.

VMware installation troubleshootingThis section provides information for specific problems and workaroundsassociated with VMware installation.

Review all troubleshooting topics for possible solutions. For additionaltroubleshooting information, see the IBM Systems Director Release Notes.

Troubleshooting and support 27

Cannot install agents on Red Hat Enterprise Linux or VMwaremanaged systems using the Agent Installation WizardThis problem affects using the Agent Installation Wizard to deploy agents onmanaged systems running Red Hat Enterprise Linux or VMware ESX.

Problem:

Attempts to install agents on Red Hat Enterprise Linux or VMware managedsystems 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: com.jcraft.jsch.JSchException: Algorithm negotiation fail

at com.jcraft.jsch.Session.receive_kexinit(Session.java:555)at com.jcraft.jsch.Session.connect(Session.java:334)at com.jcraft.jsch.Session.connect(Session.java:190)at 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 changingthe configuration of the SSH daemon on the VMware system.

Resolution:

Perform the following steps to ensure that agents can be installed on managedsystems running Red Hat Enterprise Linux or VMware ESX using the AgentInstallation 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

6. Use VMware vSphere Client Security Profile Properties to enable ibmsa andibmcim.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.

7. Ensure the validity of any stored public key data for the target system inroot_SSH_data_directory/known_hosts on IBM Systems Director Server. See“Common Agent cannot be installed on an AIX or Linux system” for moreinformation.

A Platform Agent managed system running VMware 3.5 isdiscovered as an agentless managed systemThis limitation affects Platform Agent managed systems running VMware ESX 3.5update 3.

28 IBM Systems Director Troubleshooting and Support Guide

Problem

After installing Platform Agent on a managed system running VMware ESX 3.5update 3, the managed system appears in IBM Systems Director Web interface asan 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 Webinterface.

v OpenPegasus is restarted on the managed system after installing Platform Agentbut before adding and gaining access to the managed system in IBM SystemsDirector Web interface.

Explanation

This problem occurs because the version of OpenPegasus that is included withVMware ESX 3.5 update 3 has a built-in SLP service agent. When OpenPegasusstarts, it takes control of port 427, removing the registration for the Platform Agentservice agent.

Resolution

To resolve this problem after the managed system is rebooted or afterOpenPegasus 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 managedsystem running VMware ESX 3.5 update 2 or update 3.

Windows installation troubleshootingThis section provides information for specific problems and workaroundsassociated with Windows installation.

Review all troubleshooting topics for possible solutions. For additionaltroubleshooting information, see the IBM Systems Director Release Notes.

Windows blue screen IRQL_NOT_LESS_OR_EQUALThis problem affects Common Agent. It occurs only on systems running WindowsServer 2003.

Problem

During installation of Common Agent, Windows might display the following bluescreen trap:IRQL_NOT_LESS_OR_EQUAL

Resolution

This problem is solved by a Microsoft update. See Microsoft Knowledge BaseArticle 825236 for more information.

Troubleshooting and support 29

Cannot connect to agents after migration from 6.1.x to 6.2If you migrate IBM Systems Director Server from 6.1.x to 6.2 and change thelocation of the product, connectivity problems can result.

Problem

If you use Common Agent, IBM Systems Director Server cannot connect to andmanage the local embedded agent if the location of the IBM Systems DirectorServer installation is moved during migration.

Explanation

If you migrate and change the location of the product, particularly if you move anembedded 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 -forceconfigure.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 thesecond password used while installing IBM Systems Director Server (agentmanager) using the advanced wizard path. If you used the basic installationpath, it is the operating system's administrator password.

v If your server does not run on Windows, it is the second password enteredduring the configAgtMgr.sh step during the IBM Systems Director Serverinstallation.

3. If your server does not run on Windows, replace configure.bat withconfigure.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.2If you change agent managers on IBM Systems Director 6.1.x and then upgrade itto IBM Systems Director 6.2, the agents that the previous agent manager managedmight not migrate.

Problem

When migrating IBM Systems Director 6.1.x to 6.2, agents that were managed by aprevious agent manager on IBM Systems Director 6.1.x are not migrated.

Explanation

If you add another agent manager to IBM Systems Director 6.1.x and activate it,the agents that were managed by the previous agent manager are notautomatically set up migrated. This causes problems when you perform tasks suchas upgrading to IBM Systems Director 6.2. To migrate the agents with IBM Systems

30 IBM Systems Director Troubleshooting and Support Guide

Director, you need to ensure that they are associated with the active agentmanager.

Resolution

Complete the following steps to migrate all agents that were managed by thepreviously active agent manager to the new active agent manager before youmigrate IBM Systems Director:1. Run the following commands:

configure.bat -unmanaged -forceconfigure.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 thesecond password used while installing IBM Systems Director Server (agentmanager) using the advanced wizard path. If you used the basic installationpath, it is the operating system's administrator password.

v If your server does not run on Windows, it is the second password enteredduring the configAgtMgr.sh step during the IBM Systems Director Serverinstallation.

2. If your server does not run on Windows, replace configure.bat withconfigure.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.2without the agents, you need to manually migrate the agents to the new activeagent manager.

Cannot upgrade Common Agent from 6.2 to 6.3.x on IPv6-onlymanaged system

This issue affects an IPv6-only managed system running AIX 6.2.

Problem

When upgrading Common Agent from 6.2 to 6.3.x on an IPv6-only managedsystem running AIX 6.1, the upgrade fails. Running the command/opt/ibm/director/agent/bin/lwistatus.sh returns ALR1327E: Access denied. Inaddition, the nonstop and LWI processes do not stop as they should during anupgrade of Common Agent.

Resolution

After starting the Common Agent installation to upgrade the managed system, youmust manually kill all of the non-stop and Common Agent processes bycompleting the following steps:1. Find the non-stop processes by running the following command:

ps -ef | grep nonstop_aix

2. Find the Common Agent processes by running the following command:ps -ef | grep /var/opt/tivoli/ep/_jvm/jre/bin/java

3. Run kill -9 to terminate the non-stop and Common Agent processes.

Troubleshooting and support 31

Cannot install agent on managed systemThis problem affects installation of agent packages on managed systems using theAgent Installation Wizard from a management server running AIX or Linux.

ProblemWhen you attempt to install an agent package on a managed system, the packageis not installed.

InvestigationUse 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 step4.

v If the status of the agent installation task is not Complete with errors, thenthe problem you encountered is not described in this topic. Review the otherinstallation troubleshooting topics or see “Getting help and support”.

4. Right-click the job activation record for the agent installation task and clickShow logs. The log is displayed below the table.

5. Look for either of the following messages in the log for the agent installationthat could not be completed:scp: /tmp/commonagent_tmp/dir6.1_commonagent_linz.sh: No such file or directory

orFile 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 encounteredis not described in this topic. Review the other installation troubleshootingtopics or see “Getting help and support.”

ExplanationThe Expect package (version 5.42 or later) must be installed on the managementserver in order to distribute agent packages to managed systems using the AgentInstallation Wizard. This package is either missing or corrupted.

Resolution1. 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 ofcreating a new job using the Agent Installation Wizard. Click TaskManagement > Active and Scheduled Jobs, select the agent installation jobthat did not complete successfully, and then click Run Now.

32 IBM Systems Director Troubleshooting and Support Guide

Installing a version of IBM Systems Director that is earlierthan 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 problemsinstalling another, earlier version of IBM Systems Director. The existing version ofIBM Systems Director becomes disabled and the newly-installed earlier versiondoes not work (twgstart fails).

Explanation

You cannot directly install a version of IBM Systems Director on a system thatalready contains a later version of IBM Systems Director than the one you want toinstall. You must first completely uninstall the existing IBM Systems Directorversion, including all data, before installing the earlier IBM Systems Directorversion.

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 Directorversions.

3. Install the earlier IBM Systems Director version.

IBM Systems Director installation hangs and then failsThis problem affects all systems.

Problem

The IBM Systems Director installation process hangs for 30 minutes or more andthen fails with the following error:LWI is taking too long to start. Installer Exiting...

Investigation

The increased installation duration might result from an incorrectly configurednameserver (DNS) on the system or, if a nameserver is not required for yourinstallation, 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 configurednameserver is likely the cause.

Troubleshooting and support 33

Explanation

When starting the server during IBM Systems Director installation, a number ofsockets are created. The sockets need to lookup network addresses. If thenameserver is improperly configured, the lookup time duration will be very longand the lookup will then usually fail. This will cause IBM Systems Director Serverto 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, completethe 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.

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/hostsv Windows: %SystemRoot%\system32\drivers\etc\hosts

Example:129.0.2.1 localhost10.122.126.11 director_server

2. Try installing IBM Systems Director again.

Additional information

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 andrequires cleanup

This problem affects systems on which installation or the removal of an installationfailed for a component of IBM Systems Director.

Problem

You attempted to install IBM Systems Director or uninstall a component of IBMSystems Director, but it failed and left behind files, data, or registry settings thatmight cause problems for later installations.

Explanation

A failed IBM Systems Director installation or uninstallation can leave items thatrequire cleanup.

34 IBM Systems Director Troubleshooting and Support Guide

Resolution

Use the following information to clean up after a failed IBM Systems Directorinstallation or uninstallation:

For AIX:If the installation or uninstallation of one or more of the IBM SystemsDirector file sets fails, perform a reboot and take the following actions toclean 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 -l | grep -i fspproxy* lslpp -l | grep -i director* lslpp -l | grep -i cas* lslpp -l | grep -i sysmgt.cim* lslpp -l | grep -i tivguid

If any of the following file sets are returned by the lslpp command, usethe installp -u <filesetname> command to uninstall them in the orderin which they are listed here:– Director.Server.ext.FSPProxy.rte– DirectorServer– DirectorCommonAgent– cas.agent*

Important: If you did not uninstall dependent file sets first, use theinstallp -ug cas.agent command to uninstall them along with thecas.agent file set.

– 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.cim.providers.metrics*

– sysmgt.cim.providers.scc*

– sysmgt.cimserver.pegasus.rte*

– tivoli.tivguid*

* Other applications might use these file sets, so remove them withcaution.

v After uninstallation, complete the following steps to check forunnecessary remaining processes and end them if they are found:1. Check for CIMprocesses by running the following commands:

# ps -ef | grep cimserverroot 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 diagroot 487444 1 0 Oct 15 - 0:00

/opt/freeware/cimom/pegasus/bin/CIM_diagd

Troubleshooting and support 35

2. Check for SLP and SNMP processes by running the followingcommands:# ps -ef | grep tier1slproot 442594 1 0 Oct 15 - 0:00 /opt/ibm/director/cimom

/bin/tier1slp# ps -ef | grep dirsnmproot 303210 1 0 Oct 15 - 0:00

/opt/ibm/icc/cimom/bin/dirsnmpd

Note: The dirsnmpd process is required to complete IBM SystemsDirector installation on AIX. If dirsnmpd is, for whatever reason, notstarted after the installation, issue startsrc -t dirsnmpd to start itmanually.

3. Check for server Java processes by running the following commands:# ps -ef | grep java | grep -i /opt/ibm/director/jreroot 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.jarcom.ibm.lwi.LaunchLWI

4. If a common agent file set was uninstalled, check for agent Javaprocesses by running the following commands:# ps -ef | grep nonstoproot 532710 1 0 10:02:02 - 0:00 bin/nonstop_aix @config

/nonstop.properties# ps -ef | grep /var/opt/tivoli/eproot 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/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 be empty ornonexistent. Remove them if they still exist.– /opt/ibm/director/* , except for /opt/ibm/director/classes (see the

next post-uninstallation bullet for information about/opt/ibm/director/classes)

– /opt/ibm/icc– /opt/freeware/cimom/pegasus (only if sysmgt.cim* file sets were

removed)– /etc/ibm/director– /etc/ibm/tivoli– /usr/tivoli/guid (only if tivoli.tivguid was removed)– /usr/pegasus (only if sysmgt.cim* file sets were removed)– /var/opt/tivoli/ep (only if cas.agent file set was removed)

Note: Removing these files can produce related SWVPD error messageswhen you try a new installation. However, you can usually ignore theseerror messages because the SWVPD inventory is corrected as part of thenew installation process.

36 IBM Systems Director Troubleshooting and Support Guide

v After uninstallation, remove the following files only if you are running aversion of AIX that is earlier than 6.1:– /opt/ibm/director/classes/pConsoleLaunch.jar– /opt/ibm/director/classes/extensions/pConsole.TWGExt– /opt/ibm/director/classes/extensions/pConsole.TWGSubagent

For more information about cleaning up a failed installation, see Cleaningup a failed software installation in the IBM System p® and AIX InformationCenter.

For IBM i:If IBM Systems Director uninstallation fails on IBM i because an object islocked, 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 objectlocks. If a different server has a lock on an IBM Systems Director object,the uninstallation might be completed successfully but the locked IBMSystems Director object might still exist after the uninstallation. If youwant to clean up the locked objects, you first might need to end that serverto release the locks. Use the normal documented method of ending thatserver, for example, use ENDTCPSVR instead of ENDJOB.

For Linux and VMware:The IBM Systems Director uninstallation script checks for any RPMdependencies. If dependencies are detected, the script lists thedependencies found and then exits. To remove the dependencies, type thefollowing 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 -efrpm_name --noscripts where rpm_name is the dependency.

After removing all of the dependencies, run the IBM Systems Directoruninstallation script again.

For Windows:Contact the IBM Technical Support Center for assistance. You must have anIBM Support Line contract.

Network outage while installing IBM Systems Director ServerThis problem affects the re-installation after the first failed installation of IBMSystems Director Server.

Problem

When a network outage occurs during the installation process, it might cause thefile set to stay at either the BROKEN or APPLYING state.

Explanation

You might experience this problem if, while you are running the IBM SystemsDirector Server installer from a remote command line, there is a network outagethat disconnects you from the remote system.

Troubleshooting and support 37

Resolution

You must uninstall the incomplete IBM Systems Director Server before attemptingto 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” onpage 34.

Installation fails when contacting an agent managerThis problem affects server installation on all platforms.

Problem

CAS installation fails when it tries to contact the agent manager that was specifiedduring 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 actuallyinvalid, 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 aninvalid agent manager ip address or host name, correct that value to a valid agentmanager ip address or host name and reinstall IBM Systems Director.

Uninstallation of Common Agent on SUSE Linux EnterpriseServer 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 SUSELinux Enterprise Server 9 for System x system, uninstalling Common Agent willtake approximately one hour. The exact time duration of the uninstallation mightvary depending on the hardware configuration of the system on which CommonAgent was running.

Investigation

No root cause has been identified.

Explanation

If Common Agent has not been discovered at all after the installation, theuninstallation will take only a few minutes. Once it is discovered, however, theuninstallation takes much longer. This problem does not occur on other operatingsystems such as SUSE Linux Enterprise Server 10, Red Hat Enterprise Linux, orWindows.

38 IBM Systems Director Troubleshooting and Support Guide

Resolution

Plan for the uninstallation to take a while and then wait while it completes.

Silent installation does not verify settings before installingThis problem affects the silent installation of IBM Systems Director on allsupported systems.

Problem

When you perform a silent installation of IBM Systems Director with customizedsettings, the installation is interrupted after already installing some components.

Explanation

When IBM Systems Director is installed silently, it does not check the settingsbefore it starts the installation. If any of your customized settings are incorrect, theinstallation is interrupted at the point of the setting's implementation andpotentially after some components are installed.

Resolution

Check the customized settings and correct any that are wrong. Then rerun thesilent installation.

Configuration data is not preserved after uninstalling IBMSystems 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 onSystem x system, no configuration data is preserved.

Explanation

When the uninstall command is launched, the task to save the configuration datais not launched.

Resolution

If you require the configuration data for another use, ensure that you back it upmanually before you uninstall IBM Systems Director.

CIT service error displayed in Event Viewer when installingCAS agent on Windows Server 2008

This problems occurs during the installation of the CAS agent on the 64 bit versionof Windows Server 2008.

Problem

After completing the CAS agent installation on the 64 bit version of WindowsServer 2008 there are two referencing the CITMDRV service on the "AdministrativeEvents" view on in the Event Viewer.

Troubleshooting and support 39

Resolution

The errors can be safely ignored. They do not cause the installation to fail, or affectany function.

A return code with no message text is displayed whendeploying Windows agent packages

This issue affects the deployment of Windows agent packages.

Problem

When deploying Windows agent packages, the Agent installation may display areturn 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.

Unknown error message is displayed when using SLESThere is a problem with SLES that causes an IBM Systems Director to beconfigured incorrectly.

Problem

When you start IBM Systems Director, an Unknown error message is displayed onmultiple task views.

Resolution

To resolve this problem, follow these 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 positionof the entry, for example:# 127.0.0.2 server.company.com server

2. Use the smstop command to stop the management server. For moreinformation, see “smstop command” in the IBM Systems Director CommandsReference.

3. Use the smstart command to restart the management server. For moreinformation, see “smstart command” in the IBM Systems Director CommandsReference.

4. Open the IBM Systems Director Web interface and start the affected task again.

Database configuration troubleshootingThis section provides information about problems and workarounds for databasesused with IBM Systems Director. These problems include database configuration.

Errors occur during the Oracle® Database configurationThis problem affects Oracle® Database databases only.

40 IBM Systems Director Troubleshooting and Support Guide

Problem

When an Oracle® Database database is used, errors occur during the databaseconfiguration process.

Investigation

Configure and start the Oracle® Database TCP/IP listener before starting thedatabase configuration task. If a failure occurs, check the configuration of theTCP/IP listener.

ORA-00257 error from the Oracle® DatabaseThis problem affects management servers that use the Oracle® Database only.

Problem

After running an SMCLI command, you are unable to start IBM Systems Director,and you receive an ORA-00257 error from the Oracle® Database.

Explanation

Some SMCLI commands are data intensive and can cause an archival error. In thiscase, the Oracle® Database fails to start due to an ORA-0257 error. After thedatabase fails, IBM Systems Director cannot be accessed. The error might indicatethat there is insufficient disk space for the archive process.

Resolution

Determine whether there is insufficient disk space for the archive process byrunning SQL> SELECT * FROM V$FLASH_RECOVERY_AREA_USAGE. If there is insufficientdisk space, you need to create sufficient disk space and ensure that the databasestarts without errors. You can try using any of the following commands to createsufficient disk space for the redo log process:SQL> archive log list;SQL> show parameter db_recovery_file_dest;SQL> SELECT * FROM V$RECOVERY_FILE_DEST;SQL> alter system archive log all;SQL> alter system set LOG_ARCHIVE_DEST_.. = ’location=/archivelogpath reopen’;SQL> alter system switch logfile

ORA-00604 error from the Oracle® DatabaseThis problem affects management servers that use the Oracle® Database only.

Problem

By default, IBM Systems Director caches prepared statements that typically open acursor with the database. The number of open cursors can grow to exceed themaximum defined for the database, resulting in a ORA-00604 error from theOracle® Database.

Resolution

Increase the Oracle OPEN_CURSORS property or change the IBM Systems Directorstatement cache size in /lwi/conf/overrides/database.properties file. To changethe OPEN_CURSORS property, either update the Oracle® Database init.ora file oruse the ALTER SYSTEM command to update the SPFILE (System Parameter File).

Troubleshooting and support 41

It is recommended that you specify an OPEN_CURSORS value that is 25% largerthan the maximum number of statements IBM Systems Director will cache. Thiscan be calculated by taking the sum of the products of the maxActive andmaxOpenPreparedStatement properties for each definition in thedatabase.properties file. The following examples illustrates how to calculate theOPEN_CURSORS value.=================================rcs.maxActive = 3rcs.maxOpenPreparedStatements = 1000

usmi.maxActive = 3usmi.maxOpenPreparedStatements = 200=================================

OPEN_CURSORS setting = ((3*100) + (3*200)) * 1.25

Oracle® Database 10g Release 2 administrator client will notinstall on Red Hat Enterprise Linux, version 5.0, or SUSELinux Enterprise Server 10

This problem affects Red Hat Enterprise Linux, version 5.0, and SUSE LinuxEnterprise 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 RedHat Enterprise Linux, version 5.0, or SUSE Linux Enterprise Server 10, theinstallation fails and indicates that the operating system is not supported with thefollowing error message:./runInstallerStarting 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-2Failed <<<<

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 makeprovisions for installing the client on those operating systems.

Resolution

You need to work around this issue until Oracle® develops a permanent solutionfor the problem. Choose one of the following two solutions and complete the stepsto bypass the operating system check during the client installation:

Solution 1 (recommended): Skip the operating system checkRun 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 assupported

42 IBM Systems Director Troubleshooting and Support Guide

Note: This is a detailed example of the workaround for Red Hat EnterpriseLinux, version 5.0, though it might also work for SUSE Linux EnterpriseServer 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:

v If you are installing Oracle® Database 10.2 from the DVD, copy the<path>/database/install/oraparam.ini file (where <path> is the baselocation of the OUI; the location into which you unzipped theinstallation files) to a temporary directory, for example to /tmp.

v If you are installing Oracle® Database 10.2 from an OTN downloador have copied the Oracle® Database 10.2 media to disk, take abackup 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 thefollowing 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, juststart 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 9checking starts, which will serve as the location of a new section ofcode:...<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" />

Troubleshooting and support 43

</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" /><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 therefhost.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® Database10.2 software installation.

Note: After you complete this workaround, you still might encounter errorsduring installation. If so, see “Oracle Database 10g Release 2 administrator clientinstallation on Linux on Power Systems throws errors” for further information.

Oracle® Database 10g Release 2 administrator clientinstallation on Linux on Power Systems throws errors

This problem affects Red Hat Enterprise Linux, version 5.0, SUSE Linux EnterpriseServer 10, and SUSE Linux Enterprise Server 11 on Linux on Power Systems afteryou have already implemented the workaround described in “Oracle Database 10gRelease 2 administrator client will not install on Red Hat Enterprise Linux, version5.0, or SUSE Linux Enterprise Server 10”.

Problem

After you have already implemented the workaround described in “OracleDatabase 10g Release 2 administrator client will not install on Red Hat EnterpriseLinux, version 5.0, or SUSE Linux Enterprise Server 10” and the Oracle® Database10g Release 2 administrator client installer passes the prerequisite check and beginsinstalling on Linux on Power Systems, you might encounter make or link errors.

44 IBM Systems Director Troubleshooting and Support Guide

Explanation

These errors might occur because additional prerequisite rpms were not installedon the system before beginning the Oracle® Database 10g Release 2 administratorclient installation.

Resolution

Complete the following steps to resolve this issue.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 installIBM XL C/C++ Advanced Edition V7.0 or you will see link errors duringinstallation. You can download the product and view installation instructionson the IBM Systems Director Downloads Web Site at www.ibm.com/systems/management/director/downloads/. Ensure that the following packages areinstalled on your operating system:v IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment

Componentv xlsmp.msg.rte-1.5.1-3v xlsmp.rte-1.5.1-3v vacpp.rte-7.0.1-3v 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 thatthe user has write permission to this directory. When you create the “oracle”user, Linux usually creates the home directory automatically, but you shouldalways verify this.

Important: IBM XL C/C++ Advanced Edition V7.0 for Linux RuntimeEnvironment Component is not completely compatible with SUSE Linux EnterpriseServer 10 or SUSE Linux Enterprise Server 11. Therefore, you need to force theinstallation of these packages on the operating system. Although there are IBM XLC/C++ packages that compatible with SUSE Linux Enterprise Server 10 and SUSELinux Enterprise Server 11, you will receive link errors during installation of theOracle® Database 10g2 client if you install them. Use the --nodeps option to install,as in the following example:rpm -ivh xlsmp.msg.rte-1.5.0-5.ppc64.rpmrpm -ivh xlsmp.rte-1.5.0-5.ppc64.rpm --nodepsrpm -ivh vacpp.rte-7.0.0-5.ppc64.rpm --nodepsrpm -ivh vac.lib-7.0.0-0.ppc64.rpm --nodeps

Unable to connect to the databaseIBM Systems Director is unable to connect to the database or loses databaseconnectivity.

Problem

If IBM Systems Director is unable to connect to the database or loses connectivity,unexpected results may occur. This could be caused by

Troubleshooting and support 45

v Improper database configuration during installation.v Errors when switching to a new database.v Network problems.v Errors with the database itself.

Investigation

Database problems will result in entries in the IBM Systems Director error logs. Bydefault, these logs are stored in install_path\lwi\logs. Database error log entriesare normally identified by ?SQLException? preceding the actual error text. If theerror message itself does not seem to clearly identify the problem, a web search forthe error text can sometimes prove useful. The accompanying stack trace may alsobe used to further identify the problem. For instance, if the stack trace contained amethod name of ?getConnection?, it could be assumed that IBM Systems Directoris having problems connecting to the database. If there are method names like?executeQuery?, ?insert?, ?update?, or ?delete?, those would imply IBM SystemsDirector had successfully obtained a connection at one point and is now trying touse it.

If you are having problems starting the server on an AIX or Linux system that usesIBM 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. Ifyou see this message, review your environment variables to ensure that theLD_LIBRARY_PATH (for Linux) or LIBPATH (for AIX) environment variable is setproperly. On 64-bit systems, the environment variables must point to the 64-bitdatabase library versions.

If the errors occur on IBM Systems Director startup and appear to be“getConnection” problems, then the database configuration would be the mostcommon problem. Consult the documentation for database configuration for moreinformation.

If the configuration steps have been correctly followed, then ensure that thedatabase itself is functional. Additional information may be found in the logsspecific to the database you are using. If you are using the supplied Derbydatabase, the log would be in install_path\lwi\logs as derby.log. For the otherdatabases (IBM DB2, Oracle, and SQLServer) the database administrator may needto be contacted.

If the errors occur after IBM Systems Director has been running successfully, thenthe problem would most likely be a network problem if the database is remote, ora problem with the database itself. These would also require examination of thevarious log files and possible database administrator involvement.

Explanation

The symptoms of database connection problems vary. If the database wasimproperly configured during installation or after switching to a new database,IBM Systems Director may not fully start. The same may hold true if the databaseitself is not functioning. If the database is on a remote machine, then networkproblems at IBM Systems Director startup may also cause IBM Systems Director tonot fully start.

46 IBM Systems Director Troubleshooting and Support Guide

Database data is not displayed after database restartThis problem affects IBM Systems Director on all platforms

Problem

While IBM Systems Director Server is active, connectivity to the underlyingdatabase is lost. Loss of connectivity can result from any number of situations,including but not limited to network problems, database server problems, andauthentication problems. After database connectivity is recovered (by restarting thedatabase application server, recovering the network issue, or so on), however, allIBM Systems Director Web interface pages that should display informationretrieved 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 IBMSystems Director in an unknown state.

Resolution

Stop IBM Systems Director Server, ensure that the database is available andaccessible, then restart IBM Systems Director Server.

Poor Performance when the IBM Systems Director server isconfigured with Microsoft SQL Server 2005 configuration

The web console or command line interface for IBM Systems Director Server maybecome slow to respond when configured with a Microsoft SQL 2005 Server.

Problem

The web console or command line interface for IBM Systems Director Server maybecome slow to respond when configured with a Microsoft SQL Server 2005. Aftera period of inactivity, the smcli and Web console may hang or become slow torespond during operations requiring access to a remote Microsoft SQL Server 2005Server. Note: The Web console responses may appear normal until an SQL access isrequired. 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 = truercs.validationQuery = select 1

rcs.testWhileIdle=truercs.timeBetweenEvictionRunsMillis=60000rcs.minEvictableIdleTimeMillis=300000

usmi.testOnBorrow = trueusmi.validationQuery = select 1

Troubleshooting and support 47

usmi.testWhileIdle=trueusmi.timeBetweenEvictionRunsMillis=60000usmi.minEvictableIdleTimeMillis=300000

The IBM Systems Director Server must be restarted for the changes to take effect.

smrestore fails when IBM DB2 is configured to requireapproval of restore operation

This problem affects IBM Systems Director with IBM DB2.

Problem

If your IBM DB2 database was configured to require approval of restoreoperations, the smrestore command will fail during upgrade to IBM SystemsDirector 6.2.

Explanation

The smrestore command begins the process of restoring data. For IBM DB2, thisprocess includes a rollforward operation. If approval is required, the rollforwardoperation cannot complete without user intervention, and therefore the process ofrestoring data cannot complete. This causes smrestore to fail.

Resolution

If your database was configured to require approval of restore operations, youshould 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 thename 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 toRECOVER or a state other than OFF, this indicates that the data cannot berestored without user intervention. smrestore fails to handle this situation.

v To resolve the issue when smrestore fails to restore the database becauseapproval 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 Directorinstallation. 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 1024PARALLELISM 1 WITHOUT PROMPTING

2. Edit the script with a text editor and change the value to include the WITHOUTROLLING 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 1024PARALLELISM 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 LOGARCHMETH2parameter to OFF. To set a parameter to OFF, run the following command on

48 IBM Systems Director Troubleshooting and Support Guide

your IBM DB2 server, where db_name is the name of your IBM Systems Directordatabase, and log_parameter is the parameter that must be set to OFF:db2 update db cfg for db_name using log_parameter no

Problems logging in troubleshootingThis section provides information about problems logging into IBM SystemsDirector Server.

Unable to access Log in page for IBM Systems DirectorThis 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 administratorhas replaced the certificate. The browser configuration determines how the browserhandles Web pages that use self-signed certificates. If the browser does not allowyou to decide whether the certificate can be trusted, then you might not be able todisplay the Web page with your current Web-browser settings.

Explanation

A self-signed certificate created and used initially by IBM Systems Directortypically will not be marked as trusted by your browser. If your browser permitsyou to add an exception and therefore mark the certificate as trusted, you cancontinue.

Resolution

If, when a self-signed certificate is detected, your browser is configured to displaya message and not continue, then no link is provided by the browser to add anexception.

Note: The browser also might have this behavior after updating to a newerversion of the browser.

If your browser is configured to display an error message with a link that permitsadding an exception, but the browser only displays an error message, changing thespecific value for browser.xul.error_pages.enabled and then changing it back mightmake the browser work correctly. Before changing your browser in about:config,see http://kb.mozillazine.org/Browser.xul.error_pages.enabled.

Additional information

To permanently avoid this problem, replace the self-signed certificate with onecreated by a Certificate Authority that Web browsers already trust. You canpurchase and use a certificate from a public Certificate Authority.

To temporarily avoid this problem, use a different Web browser that permits youto decide whether to trust the certificate.

Troubleshooting and support 49

Logging into IBM Systems Director Server failsThis problem affects the IBM Systems Director Web interface when logging intoIBM Systems Director Server.

Problem

When you attempt to log into IBM Systems Director Server using the IBM SystemsDirector 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 orremotely.

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 username:smcli chuser -m unlock -u 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 username:

v Restart the IBM Systems Director Support Program service by typing netstart dirserver.

v In the IBM Systems Director Web interface Login window, make sureyou 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 username:

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:

50 IBM Systems Director Troubleshooting and Support Guide

Login window field Login information

User ID Domain"\"Director Service Account

Password Password

v Restart the IBM Systems Director Support Program service by typing netstart dirserver.

IBM Systems Director Server troubleshootingThis section provides information about problems and workarounds for IBMSystems Director Server.

Some IBM Systems Director Server problems might seem to be problems with theIBM Systems Director Web interface. Review all troubleshooting topics for possiblesolutions.

An IBM Systems Director Server manageable resource showsoffline 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 theoperating system shows up on the IBM Systems Director Web interface with accessLocked. After access is requested, the operating system displays OK for access anda 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 ManagementController (BMC), the operating system has IPMI Drivers loaded, and the IBMSystems Director Server doesn’t have network access to the BMC. Essentially, theIBM Systems Director Server is unable to communicate with the BMC on theserver. To investigate, you can perform the following checks:v Check that you can ping the BMC address. If you don’t know the BMC address,

show the properties for the server and see if you can ping the IP addresses listedon 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 surethe BMC is connected to the network.

v If the BMC is connected to the network, find out if it has a private IP addressthat is not accessible by the IBM Systems Director Server.

v If it doesn’t have a private IP address, it could be that it is configuredincorrectly. You will have to configure it to a IP address that the IBM SystemsDirector Server has network access to.

Explanation

IBM Systems Director Server needs network access to both the operating systemand the BMC. The BMC provides hardware management, including powering theserver on or off and receiving hardware status events. Because of BMC'smanagement functionality, IBM Systems Director Server monitor’s its connectionwith the BMC. The BMC needs to be configured with an IP that the IBM Systems

Troubleshooting and support 51

Director Server has network access to so that it can be correctly managed.

Resolution

To resolve this problem, establish network connectivity from the IBM SystemsDirector Server to the BMC on the discovered server and then perform the Verifyconnection task on the server to regain the online indication.

Note: The server access state will probably display Locked, so you will have torequest access to the server using the userid and password for the BMC. Theserver’s access state will then move to the OK state.

IBM Systems Director Server fails to startThis problem affects IBM Systems Director Server after you have reinstalled it.

Problem

After you have uninstalled and then reinstalled IBM Systems Director Server, itfails 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 trafficThis problem affects the IBM Systems Director network environment and themanagement server.

Problem

IBM Systems Director Server causes a large amount of network traffic.

Explanation

To reduce network traffic, you must disable dynamic ping.

For WindowsYou 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 thenpress 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.

52 IBM Systems Director Troubleshooting and Support Guide

6. In the Value data field, type 0.7. Click OK.8. Restart the management server.

IBM Systems Director Server not receiving event indicationsThis problem can occur on all platforms that communicate with IBM SystemsDirector Server using the Common Information Model (CIM).

Problem

You use IBM Systems Director to perform tasks, but you do not see the expectedoutcome. For example, you create a virtual server but it does not appear in IBMSystems Director. You delete a virtual server, but it is not removed from IBMSystems Director. You perform power management tasks, but the power states ofthe systems do not change.

Explanation

The system or platform manager might be unable to contact the IBM SystemsDirector Server.

Resolution

Check the following items to ensure that the system or platform manager cancommunicate 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 SystemsDirector Server” and “Ports for managed systems.”

IBM Systems Director Server restarts after unstableconditions are detected

When IBM Systems Director detects potentially unstable conditions, it willautomatically protect your system by collecting debug information and restarting.

For more information, see Planning for disaster recovery in the Planning section.

Problems exist on IBM i systems with IBM Director Agentversion 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 aremanaged 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.

Troubleshooting and support 53

Resolution

The IBM i managed systems running IBM Director Agent version 5.20 must haveCIM running to function correctly. To start the CIM server on the IBM i managedsystems, run the following IBM i command:STRTCPSVR *CIMOM

With CIM running on the managed systems, IBM Systems Director Server willgather the missing information on its next scheduled verification of the agent.

Trace and error log files are not createdIBM Systems Director trace and error log files are not created in the expecteddirectory.

Problem

If you start IBM Systems Director Server with JConsole enabled, the IBM SystemsDirector trace and error log files are not created in the install_root\lwi\logsdirectory, where install_root is the root directory of your IBM Systems Directorinstallation. 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 thepath 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 smstop

For Windows 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 SystemsDirector installation. Note that this path uses the backslash (\) to delimit thedirectory; depending on the system that you are using, you might be requiredto 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 smstart

For Windows net start DirServer

Additional information

If you want to connect from a remote JConsole, you must change a setting in theinstall_root\lwi\conf\overrides\USMIKernel.properties file, where install_root is theroot directory of your IBM Systems Director installation. Note that this path usesthe backslash (\) to delimit the directory; depending on the system that you areusing, you might be required to enter the path using the forward slash (/). Change

54 IBM Systems Director Troubleshooting and Support Guide

the default IP address in the following line to the IP address of the managementserver (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 runningThis problem affects IBM Systems Director Server.

Problem

You are not sure if IBM Systems Director Server is running.

Resolution

To check whether the management server is running, complete the followingapplicable 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 DirectorThis problem affects the IBM Systems Director Web interface and Common-Agentmanaged resources. The problem occurs only on management servers (IBMSystems Director Server) running Linux.

Problem

A user is locked out of IBM Systems Director after unsuccessfully trying five timesto log in to the IBM Systems Director Web interface.

Resolution

To correct this problem, type one of the following commands on the managementserver 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.

Additionally, ensure the following entries are contained in /etc/pam.conf:lwilogin auth required pam_aixlwilogin account required pam_aixlwilogin password required pam_aixlwilogin session required pam_aix

Troubleshooting and support 55

Additional information

Each time a user successfully or unsuccessfully attempts to log in to the IBMSystems 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 asuccessful login by editing the /etc/pam.conf file on the management server. Addthe 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 topam_tally might vary depending on your network configuration. Use theappropriate parameters and values for your network environment.

Common Agent and Platform Agent troubleshootingThis section provides information about problems and workarounds for CommonAgent and Platform Agent.

Some Common Agent and Platform Agent problems might be problems with otherIBM Systems Director components. Review all troubleshooting topics for possiblesolutions.

Extraneous CIM indication errors appear in the system log onLinux

This problem affects Platform Agent managed systems and Common Agentmanaged systems running Linux.

Problem

Extraneous error messages appear in the system log stating that the CIM serverdid 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.datfile that is used to define some default CIM indications is the same for bothWindows and Linux installations; however, the SMS consumer is not available onmanaged systems running Linux.

Resolution

The extraneous errors can be ignored.

Alternatively, you can use the cimsubscribe command to delete the subscriptionsthat are causing the extraneous error messages. From a command prompt on themanaged system, issue the following commands:cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive Failed" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive Part of Logical Drive

Failed" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive Added" -hn "SMS"

56 IBM Systems Director Troubleshooting and Support Guide

cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Hot Spare Created" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Hot Spare Failed" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive becomes Hot Spare"

-hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Logical Drive Offline" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Logical Drive Degraded" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Logical Drive Optimal" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Physical Drive PFA" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Rebuild Started" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Rebuild Complete" -hn "SMS"cimsubscribe -n root/LSI_IR_1_2_0 -ds -fn "RAID Rebuild Failed" -hn "SMS"

Managed resource does not send eventsThis problem affects managed resources running VMware ESX 3.0.

Problem

Managed resources running VMware ESX 3.0 do not send in-band events to IBMSystems 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 SystemsDirector.

Resolution

This problem is fixed by ESX Server 3.0.0 patch ESX-8005537. Obtain downloadand 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 onLinux with Xen

This limitation affects installing Common Agent on Platform Agent managedsystems running with the Xen kernel.

Problem

If you have previously installed Platform Agent on a Platform Agent managedsystem running with the Xen kernel, installing Common Agent on the managedsystem does not succeed. An error message like the following one is displayed:Promotion of IBM Systems Director Platform Agent with Xen support to IBMSystems Director Common Agent is not supported.

Explanation

When Platform Agent is installed, it installs two providers (cmpi-xen andibmvm-imagesupport) that cause conflicts when you later install Common Agent.

Resolution

Uninstall Platform Agent, and then install Common Agent.

Troubleshooting and support 57

Cannot install agents on Red Hat Enterprise Linux or VMwaremanaged systems using the Agent Installation Wizard

This problem affects using the Agent Installation Wizard to deploy agents onmanaged systems running Red Hat Enterprise Linux or VMware ESX.

ProblemAttempts to install agents on Red Hat Enterprise Linux or VMware managedsystems 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: com.jcraft.jsch.JSchException: Algorithm negotiation fail

at com.jcraft.jsch.Session.receive_kexinit(Session.java:555)at com.jcraft.jsch.Session.connect(Session.java:334)at com.jcraft.jsch.Session.connect(Session.java:190)at 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 changingthe configuration of the SSH daemon on the VMware system.

ResolutionPerform the following steps to ensure that agents can be installed on managedsystems running Red Hat Enterprise Linux or VMware ESX using the AgentInstallation 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

6. Use VMware vSphere Client Security Profile Properties to enable ibmsa andibmcim.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.

7. Ensure the validity of any stored public key data for the target system inroot_SSH_data_directory/known_hosts on IBM Systems Director Server. See“Common Agent cannot be installed on an AIX or Linux system” for moreinformation.

Cannot install agent on managed systemThis problem affects installation of agent packages on managed systems using theAgent Installation Wizard from a management server running AIX or Linux.

58 IBM Systems Director Troubleshooting and Support Guide

ProblemWhen you attempt to install an agent package on a managed system, the packageis not installed.

InvestigationUse 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 step4 on page 32.

v If the status of the agent installation task is not Complete with errors, thenthe problem you encountered is not described in this topic. Review the otherinstallation troubleshooting topics or see “Getting help and support”.

4. Right-click the job activation record for the agent installation task and clickShow logs. The log is displayed below the table.

5. Look for either of the following messages in the log for the agent installationthat could not be completed:scp: /tmp/commonagent_tmp/dir6.1_commonagent_linz.sh: No such file or directory

orFile 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 32 and the “Resolution” on page 32.

v If the messages do not occur in the logs, then the problem you encounteredis not described in this topic. Review the other installation troubleshootingtopics or see “Getting help and support.”

ExplanationThe Expect package (version 5.42 or later) must be installed on the managementserver in order to distribute agent packages to managed systems using the AgentInstallation Wizard. This package is either missing or corrupted.

Resolution1. 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 ofcreating a new job using the Agent Installation Wizard. Click TaskManagement > Active and Scheduled Jobs, select the agent installation jobthat did not complete successfully, and then click Run Now.

Common Agent cannot be installed on an AIX or Linux systemWhen installing Common Agent on an AIX or LINUX system using the AgentInstallation Wizard, the installation completes with errors, but Common Agent isnot installed on the target system.

Troubleshooting and support 59

Explanation

When installing Common Agent on an AIX or Linux system, IBM Systems Directoruses SSH to copy the installer to the target system and perform the installation. Itstores the SSH public key into the /root/.ssh/known_hosts file on the IBMSystems Director Server. If the public key stored on the IBM Systems DirectorServer is not valid, the installation of the Common Agent will not completesuccessfully.

Investigation

After the installation of Common Agent completes with errors, look for an errorsimilar 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:COPCOM123EA shell command error occurred: Exit code=255,Error stream="@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

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.

60 IBM Systems Director Troubleshooting and Support Guide

Related reference:

SSH Host Key Protection

Installing Common Agent on managed systems with IBMDirector Agent version 5.20 does not succeed

This problem affects using the Agent Installation Wizard task to install CommonAgent on managed systems with IBM Director Agent version 5.20.

Problem

When you select multiple systems on which to install Common Agent using theAgent Installation Wizard, if some systems are running IBM Director Agent version5.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 runningIBM Director Agent version 5.20.

Explanation

This is a limitation.

Resolution

When you install Common Agent on systems that are running IBM Director Agentversion 5.20, ensure that all the selected systems are running IBM Director Agentversion 5.20, and wait for the installations to complete before beginninginstallations on other systems.

A discovered agent displays an unexpected managed systemThis problem affects Common Agent 6.1.0.3 on AIX.

Problem

An agent is discovered with an unexpected managed system after requestingaccess.

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 isdownloaded from the Web. The agent is discovered with an unexpected managedsystem after requesting access. This problem does not exist if you install CommonAgent 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 runningthe following two commands:

Troubleshooting and support 61

INSTALL_ROOT/agent/runtime/agent/bin/endpoint.sh stopINSTALL_ROOT/agent/runtime/agent/bin/endpoint.sh start

If you installed Common Agent 6.1.0.3 manually from the image on the Web andsee 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 VMwareESX Server 3.5 or Red Hat Enterprise Linux 5.3 hosts

This problem affects upgrades of managed resources running VMware ESX Server3.5 or Red Hat Enterprise Linux 5.3.

Problem

When using the /Release Management/Agents Install/ function to upgrade anendpoint running VMware ESX Server 3.5 or Red Hat Enterprise Linux 5.3 toCommon Agent, Common Agent is not installed correctly. The uninstall script isnot available on the agent system.

Resolution

To upgrade the VMware ESX Server 3.5 host or Red Hat Enterprise Linux 5.3 hostto Common Agent, manually copy the Common Agent installer to the system andrun the installer on that system.

IBM Systems Director, version 6.1.1, Platform Agent installedon 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 installedon systems with an Integrated Management Processor (iMM).

Problem

IBM Systems Director, version 6.1.1, Platform Agent installed on systems with anIntegrated Management Processor (iMM), requires an Intelligent PlatformManagement Interface (IPMI) driver, which is distributed with the operatingSystem to generate in-band alerts.

Explanation

Base Windows 2003 operating systems installed on systems with iMM will not beable to generate in-band alerts. However, iMM on systems with Windows 2003 willsend out-of-band alerts to IBM Systems Director Server to prevent users fromlosing functionality.

62 IBM Systems Director Troubleshooting and Support Guide

Resolution

To enable IPMI driver on Windows 2008 and Windows 2003 R2, see “ManagingIPMI Devices in Windows 2003 R2 and Windows 2008” in the IBM SystemsDirector Best Practices RedWiki.

Linux and VMware operating systems can use openIPMI driver, which isdistributed with the operating system itself.

Platform Agent 5.20.3x installation fails on systems with CitrixXenApp

This problem affects IBM Systems Director 6.1 systems that use the Citrix XenAppdrive 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 theintended installation drive, but the regular installation of Platform Agent 5.20.3xcannot tell this and so fails.

Resolution

Install Platform Agent 5.20.3x with edited response files to point the installation tothe correct drive letter. Complete the following steps to do this for eachcomponent.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. Savethe response file.

3. Install Platform Agent 5.20.3x using the response file.

Common Agent does not start when the host name is set tolocalhost 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 thename server is not setup correctly.

Resolution

Configure the host name and name server correctly and then restart the CommonAgent.

Installation of the common agent on AIX fails to start LWIInstallation of the common agent on AIX fails with the message: LWI is takingtoo long to start.

Troubleshooting and support 63

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 IPv6loopback address is defined in its /etc/hosts, resolving ::1 might time out whenthere is a DNS configured and the DNS server is not responding to requests oftype AAAA.

Resolution1. IPv6 is enabled: if the ifconfig command returns something similar to this:

# ifconfig -a | grep inet6inet6 ::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 theaddress lookup consults /etc/hosts first before trying DNS resolution:hosts = local , bind

IBM Director Agent version 5.20.x agents automaticallychange 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 agentsmight automatically change between online and offline.

Explanation

This issue is intermittent and caused by either or both increased load or poorperformance, for example due to insufficient memory, on IBM Systems DirectorServer.

Resolution

In the IBM Systems Director Web interface, navigate to Settings > ServerPreferences and gradually increase the values of the “Verify Connection” and“Query Vital Properties” interval settings for all resource types until the issuedisappears.

Tip: A setting of one hour for the “Verify Connection” interval and six hours forthe “Query Vital Properties” interval should suffice for most environments.

Segmentation fault message is shown when stopping thecimserver

This problem affects all 6.x releases of IBM Systems Director that are on noncurrentversions of Red Hat Enterprise Linux version 4 or 5, SUSE Linux version 11, orVMware ESX Server 4.1.

64 IBM Systems Director Troubleshooting and Support Guide

Problem

While stopping the cimserver on a system that contains a Platform Agent that isrunning in “Out of process” mode, you periodically receive a segmentation faultmessage in the system event logs. This issue is seen more frequently on 64 bitsystems as opposed to 32 bit systems. Your system is not impacted since thecimserver is stopped and subsequent restarts are not affected.

Explanation

In Platform Agent, the instrumentation layer is loaded as a dynamic library by theCIM Server process. A probable cause for the issue is a limitation of the glibcversion that is used on the affected versions of Red Hat Enterprise Linux, SUSELinux, and VMware ESX Server. This limitation is resolved in glibc version2.12-1.7, which is included with, for example, Red Hat Enterprise Linux version 6.

Attention: Before you upgrade your Linux operating system, first verify that it issupported by the version of IBM Systems Director that you are implementing.

The segmentation fault occurs when the cimproagt process exits and unloads thelast loaded library. There is no memory leak due to this segmentation fault, but theprocess is unloaded poorly and causes the error message in the system logs. Thereis no related impact when the cimserver is started again. Since this issue isobserved only during the unload process while exiting the cimserver, this doesn'thave an impact on any supported Platform Agent functionality.

Similarly, when a C++ shared library is loaded with dlopen, it creates “new”storage on the heap while initializing (local) static variables. The correspondingcleanup code is not called before or during dlclose() processing. Instead,dlclose() succeeds, but the main program segment faults on exit while trying tocall “__tcf_0”, a symbol that was in the C++ shared library but is now deprecated.The static data is local to a function and its storage is allocated when symbols arecalled into the library, as opposed to being created by _init during dlopen().

Resolution

Complete either of the following two procedures to ensure that you no longerreceive the cimserver segmentation fault message:v Upgrade the glibc library that is installed on your operating system to version

2.12-1.7 or later.v Upgrade your operating system to a version that already contains a glibc library

of version 2.12-1.7 or later.

Attention: Before you upgrade your Linux operating system, first verify that it issupported by the version of IBM Systems Director that you are implementing.

For more information about this issue and its fix on Red Hat Enterprise Linux, seehttps://www.redhat.com/archives/rhsa-announce/2010-November/msg00020.html.

DNS servers are overwritten in resolv.confThis problem affects Platform Agent on Red Hat Enterprise Linux 6.x.

Troubleshooting and support 65

Problem

When installing Platform Agent on Red Hat Enterprise Linux 6.x, you notice thatDNS server values in resolv.conf are overwritten.

Explanation

The presence of certain RPMs impacts network configuration support for PlatformAgent.

Resolution

Complete the following steps to resolve this problem:1. Issue the following command to check if the NetworkManager service is stopped:

/etc/init.d/NetworkManager status

2. If the NetworkManager service is still running, stop it.3. Ensure that the NetworkManager RPMs are removed.4. See the “Preparing to install Platform Agent on Linux for System x and

x86-based systems”(publib.boulder.ibm.com/infocenter/systems/topic/UNKNOWN_PLUGIN/fqm0_t_preparing_to_install_core_on_xseries.html) topic and ensure that allother RPMs that are listed there for removal are also removed.

5. Retry Platform Agent installation.

Duplicate managed resources appear after relocating a logicalpartition from an AIX system

This problem affects Power Systems compute nodes that run AIX with CommonAgent 6.2.1 installed.

Problem

After you relocate a logical partition from a Power Systems compute node withAIX to another system, there are two managed resources listed for the same logicalpartition instead of one.

Investigation

Check the version number of the Common Agent that is installed on the AIXcompute node. If the Common Agent version is 6.2.1, an unnecessary managedresource was created for the logical partition on the AIX compute node from whichyou relocated.

Explanation

Under certain circumstances, after a logical partition is relocated and you runinventory, Common Agent version 6.2.1 might create a duplicate managed resourcefor that relocated logical partition. The managed resource on the source computenode (the AIX compute node from which the logical partition was relocated) isunnecessary and should be deleted.

Resolution

To remove the duplicate managed resource and upgrade the Common Agent from6.2.1 to 6.3.0 or later, complete the following steps:

66 IBM Systems Director Troubleshooting and Support Guide

1. Use the IBM Systems Director Web interface to remove the duplicate managedresource.

2. Download and install Common Agent 6.3.0 or later on the AIX system.

Configure Agent Manager on IBM Systems Director ServerConfiguring the Agent Manager in order to use IBM Systems Director Server.

Problem

Before using IBM Systems Director Server, the Agent Manager must be configuredproperly. In some instances Agent Manager configuration fails and requiresreconfiguration.

If Agent Manager does not work properly, then IBM Systems Director Server willhang.

Resolution

Before configuring Agent Manager

The SLP service must be available and Common Agent must work properly beforeAgent Manger can be configured. See additional information about how to ensureSLP works properly and how to ensure common agent works properly.

Clean environment for reconfiguring Agent Manager

The following steps are required to reconfigure the Agent Manager. These steps arenot required if you are configuring Agent Manager for the first time.Remove director_home/lwi/runtime/core/DATABASERemove director_home/lwi/runtime/agentmanager/eclipse/plugins/ \com.ibm.tivoli.cas.manager.certRemove director_home/lwi/runtime/agentmanager/toolkit/certs/*Remove director_home/lwi/proddata/agentmanager.propertiesRemove director_home/log/agentmanagerlock.lck

Agent Manager Configuration

For a non-Windows environment, run this command:configAgtMgr.sh

For a Windows environment, run this command:cfgServer.bat

Go to director_home/log/usmi-cas-setup.log and check usmi-cas-setup.log.Verify the overall return code is 0:

Check Agent Manager Status

Access the Agent Manager web console at http://agent_manager_ip_address:9513/AgentMgr/Info.1. netstat -na | grep 951(netstat -na|findstr 951)

This will list 9511, 9512, and 9513(*)

Troubleshooting and support 67

tcp 0 0 0.0.0.0:9514 0.0.0.0:* LISTENtcp 0 0 0.0.0.0:9515 0.0.0.0:* LISTENtcp 0 0 127.0.0.1:33343 127.0.0.1:9515 TIME_WAITtcp 0 0 127.0.0.1:47260 127.0.0.1:9514 TIME_WAITtcp 0 0 :::9510 :::* LISTENtcp 0 0 :::9511 :::* LISTENtcp 0 0 :::9512 :::* LISTENtcp 0 0 :::9513 :::* LISTEN

2. netstat -na | grep 2000(netstat -na|findstr 2000)

This lists 2000netstat -na|grep 20000tcp 0 0 :::20000 :::* LISTEN

3. smcli getAgentManagers

This returns the Agent Manager information.*******************************************Agent manager id/name : 9855B4C95D363CD1ACDA4CC9EB3E41BEAgent manager version : 1.4Agent manager ip : 2002:97d:eec3:611:e61f:13ff:fe60:1d58Is this default? : trueAgent Manager userid : rentestAgent Manager port : 9511Agent Manager ipaddress list: 2002:97d:eec3:611:e61f:13ff:fe60:1d58,9.181.137.148, 10.3.0.2, fe80:0:0:0:e61f:13ff:fe60:1d58,fe80:0:0:0:e61f:13ff:fe60:1d5a, fe80:0:0:0:ff:ffff:feff:ff01,Is this Embedded: true

4. smcli getAgents <agent_manager_id>

This returns agent information for specific agent managers.smcli getAgents 9855B4C95D363CD1ACDA4CC9EB3E41BE

Agent: https://9.181.137.148:9510/Agent: https://[2002:97d:eec3:611:e61f:13ff:fe60:1d58]:9510/Agent: https://10.3.0.2:9510/

5. Check the IBM Systems Director Server start-up log and verify there are nocas.manager related exceptions.

Additional information

Check SLP query information on IBM Systems Director Server.

On Linux, run the following command:/opt/ibm/icc/cimom/bin/slptool -u <ip> findsrvs service:management-software.IBM

Check the SLP registry. You should see the following output:service:management-software.IBM:platform-agent://10.9.7.10,6495service:management-software.IBM:usma://netth10.trow.netfinity.com,6420

On Windows or AIX, run the following command:slp_query --type=* --address=<ip>

Check the SLP registry. You should see the following output:rcc-pok-ipg-177 <opt/ibm/icc/cimom> # slp_query --type=* --address=9.12.173.1770561URL: service:management-software.IBM:platform-agent://9.12.173.177ATTR: (vendor=IBM),(version=6.2.1),(uid=7F3347EDF143736B),(ip-

68 IBM Systems Director Troubleshooting and Support Guide

address=9.12.173.177),(hostname=rcc-pok-ipg-177.cloud9.ibm.com)URL: service:wbem:http://9.12.173.177:5988ATTR: (template-url-syntax=http://9.12.173.177:5988)URL: service:wbem:https://9.12.173.177:5989ATTR: (template-url-syntax=https://9.12.173.177:5989)URL: service:management-software.IBM:usma://rcc-pok-ipg-177.cloud9.ibm.comATTR: (ip-address=9.12.173.177),(mac-address=5e.3f.4f.bb.fb.2),(tivguid=D29B8AC486E811E0A2B35E3F4FBBFB02),(uid=7f3347edf143736b),(vendor=IBM),(System-Name=rcc-pok-ipg-177.cloud9.ibm.com),(timezone-offset=-240),(version=6.2.1.2),(port=9510),(manager=unmanaged)URL: service:service-agent://9.12.173.177ATTR: (service-type=service:management-software.IBM:usma,service:service-agent)

Using Common Agent

Check the following logs to verify the installation and update are successful:v Installer log /var/log/dirinst.log or windows/dirinst.log

v Feature install log agent_home/log/installfeatures*.log

v Feature update log agent_home/log/updateinstaller.log

Check the status of the common agent1. Run netstat -na. 9510, 9514, 9515 should all be listed.2. Check the agent status with the following command:

For a non-Windows environment, run this command:agent_home/runtime/agent/bin/endpoint.sh status

For a Windows environment, run this command:agent_home/runtime/agent/bin/endpoint.bat status

3. Query the common agent start-up log. Search for the keyword CoreAgent.query.If common agent is working, this term should be found within the log.

Check the common agent management status1. Run agent_home/runtime/agent/config/endpoint.properties

#certs related infoCertManagement.CRL.URI=/AgentMgr/CRLRequeststatus.lastSuccessfulContactID=30820293308201fc020152300d06092a864886f70d0101040500306131133011060a0992268993f22c6401191603636f6d31133011060a0992268993f22c640119160369626d31163014060a0992268#am host infoAgentManagerQuery.Host=9.12.181.202

AgentManagerQuery.Host is the current Agent Manager of the agent.2. You can also use Slp query to show the common agent management status.

./slptool -u 9.5.42.195 findattrs service:management-software.IBM:usma://SDMCLTPOL2(ip-address=10.3.0.2@10.128.128.5@9.5.42.195),(mac-address=E41F13674AC8),(tivguid=2C9FDDB07FD511E08C74E41F13674AC8),(uid=7f2f85092b475946),(uuid=32D4042B-F2FF-4F71-AB59-18E8A4266CD4),(vendor=IBM),(System-Name=SDMCLTPOL2),(timezone-offset=-300),(version=6.2.1),(port=9510),(manager=127.0.0.1)

3. Run smcli on IBM Systems Director Server.smcli testCoreAgentQuery<agent_ip> 9510

Troubleshooting and support 69

Web interface troubleshootingThese problems can occur when you try to open the Web interface or when youare working with your resources in the interface.

Certificate has not been signed by a trusted authorityThis problem affects Microsoft Internet Explorer and Mozilla Firefox Web browsers.

Problem

When you try to open the IBM Systems Director Web interface, the followingmessage or window is displayed:

For Microsoft Internet Explorer

A security message indicates that there is a problem with the securitycertificate; the security certificate was not issued by a trusted certificateauthority.

The message might tell you to determine whether you want to trust thecertifying authority, or it might strongly recommend that you close theWeb page. The message might be slightly different depending on theinstalled 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 SecureSockets Layer (SSL) certificate it received from the server and has determined thatthe 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 isdisplayed:

70 IBM Systems Director Troubleshooting and Support Guide

Table 1. Message descriptions and suggested actions

Message description Suggested actions

The message indicates that you can view thecertificate to determine whether you want totrust the certifying authority.

Choose one of the following actions:

Temporary solution:Click View Certificate and InstallCertificate to install the certificateand instruct the browser to trust theserver.

Permanent solution:Replace the default certificate witha certificate signed by a certificateauthority (CA). For moreinformation, see Configuring SecureSockets Layer between IBMSystems Director and the Webbrowser client.

Troubleshooting and support 71

Table 1. Message descriptions and suggested actions (continued)

Message description Suggested actions

The message provides a recommendationthat you close the Web page and do notcontinue to the Web site.

Choose one of the following actions:

Temporary solution:Complete the following steps:

1. Click Continue to this websiteto open the Web interface.Note: The message mightindicate that continuing to theWeb site is not recommended.However, you can proceed tothe Web site to login to IBMSystems Director Web interfaceand install the certificatetemporarily.

2. Login to IBM Systems DirectorWeb interface.

3. Click Certificate Error.

A message is displayedindicating that the certificatepresented by this Web site wasnot issued by a trustedcertificate authority.

4. Click View certificates.

A message is displayedindicating that the CA Rootcertificate is not trusted.

5. Click Install Certificate toinstall the certificate and instructthe browser to trust the server.

Permanent solution:Complete the following steps:

1. Click Click here to close thiswebpage.

2. Replace the default certificatewith a certificate signed by acertificate authority (CA). Formore information, seeConfiguring Secure SocketsLayer between IBM SystemsDirector and the Web browserclient.

For Mozilla FirefoxTo resolve this problem, complete the applicable step:

Temporary solution:Select Accept this certificate permanently to install the certificateand instruct the browser to trust the server, and click OK.

Permanent solution:Replace the default certificate with a certificate signed by a

72 IBM Systems Director Troubleshooting and Support Guide

certificate authority (CA). For more information, see ConfiguringSecure Sockets Layer between IBM Systems Director and the Webbrowser client.

Firebug Firefox extension might cause unpredictable behaviorin the IBM Systems Director Web interface

This problem affects Mozilla Firefox Web browsers that have the Firebug extensioninstalled.

Problem

The Firebug extension for Firefox might cause Web-browser applications to behaveerratically. If Firebug is enabled in Firefox, the IBM Systems Director Web interfacemight react slowly or have unpredictable behavior.

Resolution

To resolve this problem, disable the Firebug extension when using the IBMSystems Director Web interface. For information about disabling Firebug, see theFirebug documentation.

Inserting a variable in the Auto Rename template appears tofail

This problem affects the Edit task on the Settings > Auto Rename panel.

Problem

When adding a variable to the Auto Rename template, you may not see the newproperty in the Auto Rename template field when clicking Insert.

Resolution

When the text in the Auto Rename template field fills the text box, any newvariables appear outside the initial view of the text field. You can verify thevariable was correctly added by placing your cursor in the Auto Rename templatefield and scrolling to the end.

Internet Explorer fails to display the IBM Systems DirectorWeb interface

This problem affects Microsoft Internet Explorer 7 Web browsers that are runningon Windows Vista.

Problem

The Internet Explorer 7 Web browser fails to display and cannot login to the IBMSystems Director Web interface on a system running Windows Vista, MozillaFirefox running on the same Vista system can log into the IBM Systems DirectorWeb interface.

Resolution

Make sure that the Internet Explorer 7 Web browser uses Java 5 Service Refresh 5(SR5) or later.

Troubleshooting and support 73

Login message displays corrupt charactersAfter running the dircli chgloginmsg command, the customized login messagecontains corrupted characters for some languages.

Problem

When creating a customized login message as described in Changing the welcomemessage on the login screen, you must store the text of the message in a propertyfiles. Property files are not compiled into byte codes. Therefore, there is no way totell the Java Virtual Machine (JVM) which character set to use. When a propertyfile is loaded from a stream, the ISO 8859-1 character encoding is used. Thecharacters are corrupted if they cannot be directly represented in this encoding.

Resolution

The contents of the loginMessage_xx.properties file needs to be created in ASCIIor encoded in with Unicode-escape sequences. Initially, create the customized loginmessage file (loginMessage_xx.properties) so that it is encoded in UTF-8, thenconvert the file to escaped Unicode using a Java utility program such asnative2ascii.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-8encoded property file. For example: native2ascii –encoding UTF-8sourcefile.txt targetFile.txt

3. Run the dircli chgloginmsg command against the property file.

No results found when using Find a ResourceThis problem affects the Find a Resource task when searching for a resource with aname containing a single quote.

Problem

When trying to locate a resource that has a single quote (') in its name, if you addthe single quote character around the search string, Find a Resource will fail tofind the resource.

Resolution

To resolve this problem, search for the resource using other characters in the nameinstead of the single quote.

Panels display translated text in multiple languagesThis problem occurs only when viewing pages in the IBM Systems Director Webinterface 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 multiplelanguages. When the problem occurs, some strings may display in the newlyselected language and other strings may display in the original language.

74 IBM Systems Director Troubleshooting and Support Guide

Resolution

When you change languages for your browser, complete the following steps toensure that the IBM Systems Director Web interface does not display translatedstrings 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 languagesThis problem occurs only when viewing pages in the IBM Systems Director Webinterface in languages other than English.

Problem

When your browser is set to a non-English language, some page elements in theIBM Systems Director Web interface display truncated strings (words or phrases).The truncation is caused when the translated string is longer than the Englishstring. This kind of problem occurs most frequently in elements like table cells orbuttons. Sometimes, the panel border truncates an element that has been enlargedbecause of the longer translated string.

Resolution

Change your system to use a larger screen resolution. Changing the resolution maynot fix all occurrences of truncated text.

Panels display truncated text in non-English languagesThis problem affects the Microsoft Internet Explorer browser.

Problem

When using Internet Explorer, items in a dropdown list may be slightly cut off atthe bottom which may make it difficult to read.

Resolution

In most cases, you can resolve this by changing the text size to a smaller value. Tochange the text size, select View > Text Size from the menu bar, then selectMedium, Smaller, or Smallest. If that does not resolve the problem, you can use aMozilla Firefox browser as the problem does not occur on Firefox.

Unpredictable results occur when users log into IBM SystemsDirector Server using the same browser application

Problem

If you log into IBM Systems Director using a web browser and then log into IBMSystems Director again using the same browser application from the same system,unpredictable results, including empty web pages, may occur in both browsersessions.

Troubleshooting and support 75

Unable to export informationThis problem affects the Microsoft Internet Explorer and Mozilla Firefox Webbrowsers.

Problem

You are unable to export information from a table view or topology view in theIBM Systems Director Web interface.

Resolution

Complete the following applicable steps:

For Microsoft Internet ExplorerMake sure that the browser is set to enable automatic prompting for filedownloads. To verify, complete the following task:1. In the Security Settings - Internet Zone window, ensure that

Downloads > Automatic prompting for file downloads > Enable isselected.

2. Try the export task again.

Make sure that the option to block pop-up windows is disabled for theWeb 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 Settings window, in the Address of Web site to

allow field, type the Web address of IBM Systems Director Server.4. Click Add.5. Click Close.

Make sure that the option to save encrypted pages to disk is enabled. Toverify, complete the following steps:1. Click Tools > Internet Options.2. In the Internet Options window, click the Advanced tab.3. In the Security area, make sure that Do not save encrypted pages to

disk is deselected.4. In the Options window, click Apply and then OK.

For Mozilla FirefoxMake sure that the option to block pop-up windows is disabled for theWeb 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.

76 IBM Systems Director Troubleshooting and Support Guide

Unable to print informationThis problem affects the Microsoft Internet Explorer and Mozilla Firefox Webbrowsers.

Problem

You are unable to print information from a table view or topology view in the IBMSystems Director Web interface.

Resolution

Complete the following applicable steps:

For Microsoft Internet ExplorerMake sure that the option to block pop-up windows is disabled for theWeb 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 Settings window, in the Address of Web site to

allow field, type the Web address of IBM Systems Director Server.4. Click Add.5. Click Close.

For Mozilla FirefoxMake sure that the option to block pop-up windows is disabled for theWeb 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 asexpected when browsing

This problem affects Microsoft Internet Explorer Web browsers that have EnhancedSecurity Configuration enabled and are running on Windows Server 2003 orWindows Server 2008.

Problem

By default, Internet Explorer Enhanced Security Configuration is enabled onWindows Server 2003 and Windows Server 2008. When you start Internet Explorer,the following message is displayed:Microsoft Internet Explorer’s Enhanced Security Configuration is currently enabledon your server. This enhanced level of security reduces the risk of attack fromWeb-based content that is not secure, but it may also prevent Web sites fromdisplaying correctly and restrict access to network resources.

Troubleshooting and support 77

When using a Web browser with Enhanced Security Configuration enabled, someproperties of the IBM Systems Director Web interface might not display asexpected.

Explanation

Internet Explorer Enhanced Security Configuration establishes a configuration foryour server and for Internet Explorer that decreases the exposure of your server topotential attacks that can occur through Web content and application scripts. As aresult, some Web sites might not display or perform as expected.

Resolution

Using a server for Internet browsing is not a good security practice becauseInternet browsing increases the exposure of your server to potential securityattacks. It is a best practice recommendation that you run your Web browser on asystem that is not a server. However, if you must use a server running WindowsServer, you must turn off Internet Explorer Enhanced Security Configuration.Complete the following applicable steps to disable Internet Explorer EnhancedSecurity:

Windows Server 2003Complete 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 2008Complete 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.

Resource Explorer views not refreshing properly afterresources removed

This problem affects Resource Explorer views showing resources with multipleparent resources.

78 IBM Systems Director Troubleshooting and Support Guide

Problem

When you remove a member from a Resource Explorer view that has duplicateresources displayed in the view under different parents, or when you remove aresource that has child resources with duplicate resources displayed, the childresource indentation does not get updated correctly and the duplicate resources arenot removed from the view.

Resolution

Close and reopen the view. All parent resources will be displayed correctly withthe proper child resources.

Navigation area disappears when refreshing the browserscreen

If you click the browser refresh option while viewing Active Status from theWelcome banner area, the Navigation area might disappear. This problem occurs inboth Internet Explorer and Firefox.

Problem1. Log in to IBM Systems Director.2. From the Home page, click Problems or Compliance in the Welcome banner

area. The Active Status panel opens.3. Click the browser refresh button.4. The screen refreshes with the view of the Home page, without the Navigation

area.

Resolution

Clear cache, log off, and then log back in to IBM Systems Director.

To clear the cache from Firefox:

Select Tools > Options > Advanced > Network > Clear Now > OK

To clear the cache from Internet Explorer:

Select Tools > Internet Options > General

Firefox stores user data across multiple browser instancesThis problem affects using Mozilla Firefox to access IBM Systems Director.

Problem

Mozilla Firefox will keep users logged in to IBM Systems Director across multiplebrowser instances such as in the following examples:v When a user logs into IBM Systems Director and brings up a second browser,

IBM Systems Director will not require another login attempt.v When a user logs in and closes the browser, if a new browser window is opened

the user could find they are still logged in to IBM Systems Director.

Troubleshooting and support 79

Explanation

Due to a change in the Mozilla Firefox security policy, Mozilla Firefox is cachingthe web browser sessions.

Resolution

You can alter the Mozilla Firefox security policy to prevent this.1. Go to the Mozilla Firefox location bar and type about:config. Hit Enter.2. Click I'll be careful, I Promise!.3. Search for the preference browser.sessionstore.privacy_level.4. Double-click browser.sessionstore.privacy_level.5. Set the value to 1.

Launched tasks troubleshootingThese problems affect your browser when you try to launch a task that startsoutside the IBM Systems Director Web interface.

Contents of the launch[x].jnlp file are displayedThis 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 aredisplayed.

Explanation

The .jnlp extension is mapped incorrectly.

Resolution

To map the .jnlp extension to the Java Web Start executable file, complete thefollowing applicable step:

For Microsoft Internet ExplorerComplete the steps in “Updating the Microsoft Internet Explorer Webbrowser to use the Java Web Start program” in the IBM Systems DirectorSystems Management Guide.

For Mozilla FirefoxComplete the steps in “Updating the Firefox Web browser to use the JavaWeb Start program” in the IBM Systems Director Systems Management Guide.

Cannot start DS storage manager when using WindowsInternet Explorer 8

You need to change the Internet Explorer security settings before launching StorageDS Storage Manager.

Details

The default configuration of Internet Explorer 8 disables the "Automatic promptingfor file downloads" option.

80 IBM Systems Director Troubleshooting and Support Guide

Resolution1. From Internet Explorer, open Tools > Internet Options > Security > Custom

Level.2. Scroll down to the Downloads section. Under the Automatic prompting for

file downloads option, select Enable and click OK.3. Restart Internet Explorer.4. Retry launching the task.

A download window is displayedThis 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) Downloadsv (Firefox) Download Managerv (Internet Explorer) File Download

In Internet Explorer, a message might be displayed that asks if you want to save afile or indicates a file cannot be downloaded from the server.

Resolution

To resolve this problem, complete the following steps:

For FirefoxComplete the following steps:1. In the browser, click Tools > Options.2. In the Options window, click the General tab.3. Clear the Show Download Manager when a download begins check

box.4. Click OK.

For Internet ExplorerComplete 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 accesssoftware updates for Internet Explorer.

v Java Web Start (JWS) software is required to launch tasks that startoutside of the IBM Systems Director Web interface. If the error messageincludes a link to a Web site, click the link to download JWS.Alternatively, complete the steps in “Downloading Java Web Start” inthe IBM Systems Director Systems Management Guide.

v Click Tools > Internet Options > Advanced. Make sure that Do notsave encrypted pages to disk is not selected.

v The .jnlp extension might not be mapped to the Java Web Startexecutable file.To map the .jnlp extension to the Java Web Start executable file,complete the procedure detailed in “Updating the Microsoft InternetExplorer Web browser to use the Java Web Start program” in the IBMSystems Director Systems Management Guide.

v The .jnlp extension is mapped to the Java Web Start executable file, butthe Launch action is not defined.

Troubleshooting and support 81

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 onyour 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 happensThis problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem

When you try to start a launched task, an empty window is displayed or nothinghappens 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 launch tasks that startoutside of the IBM Systems Director Web interface. If the error messageincludes a link to a Web site, click the link to download JWS.Alternatively, complete the steps in “Downloading Java Web Start” inthe IBM Systems Director Systems Management Guide.

v Make sure that the system on which IBM Systems Director Server isinstalled is not blocked by a pop-up blocker on your browser system.For example, check for a pop-up blocker displayed under the Addressbar, and make sure it is turned off.

For Internet Explorer

v Click Tools > Internet Options > Advanced. Make sure that Do notsave encrypted pages to disk is not selected.

v (Internet Explorer 7 or later only) Complete the following steps:1. Click Tools > Internet Options > Security.2. Click Custom level.

82 IBM Systems Director Troubleshooting and Support Guide

3. In the Security Settings - Internet Zone window, make sure thatDownloads > Automatic prompting for file downloads > Enable isselected.

v The .jnlp extension might not be mapped to the Java Web Startexecutable file.To map the .jnlp extension to the Java Web Start executable file,complete the procedure detailed in “Updating the Microsoft InternetExplorer Web browser to use the Java Web Start program” in the IBMSystems Director Systems Management Guide.

v The .jnlp extension is mapped to the Java Web Start executable file, butthe 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 onyour 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.

For Mozilla FirefoxComplete the procedure detailed in “Updating the Firefox Web browser touse the Java Web Start program” in the IBM Systems Director SystemsManagement 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 makesure that the launched task can proceed and that this message will not bedisplayed in the future, it is recommended that you select Open with JavaWeb Start Executable and Do this automatically for files like this fromnow on.

A host name mismatch is detectedThis 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

Troubleshooting and support 83

The message indicates that the host name in the server security certificate does notmatch 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 theWeb 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 serversystem.

Notes:

1. The message might be slightly different depending on the installed version ofJava Runtime Environment (JRE) and the provider.

2. (Windows only) The Warning - HTTPS: Hostname Mismatch message windowmight be hidden behind the browser window. In this case, the Web interfaceseems to hang. Press Alt + Tab on the keyboard to bring the message windowto the foreground.

Resolution

You must change either the CN in the SSL certificate to match the host name in theURL, or you must change the host name in the URL to match the CN. The CNdesignated in the IBM Systems Director default certificate is set to the long nameof the host system. For more information about how to change the CN in the SSLcertificate, see “Configuring Secure Sockets Layer (SSL) between IBM SystemsDirector and the Web browser client” in the IBM Systems Director SystemsManagement Guide.

Java Web Start - Download Error window is displayedThis problem affects the Mozilla Firefox and Microsoft Internet Explorer browsers.

Problem

When you try to start a launched task, the Java Web Start - Download Errorwindow is displayed. The message indicates that Java Web Start is unable tolaunch the task.

Explanation

For Mozilla Firefox browsers, this message is displayed when you receive theOpening launch.jnlp message and choose to run the javaws executable from anon-system Java Runtime Environment (JRE), such as the IBM Systems DirectorJRE.

This message can also be displayed when Microsoft Internet Explorer is configuredto use a Web proxy server that is running Microsoft Internet Security andAcceleration (ISA) Server or Microsoft Forefront Threat Management Gateway,Medium Business Edition, and when no exception has been made for launchedtasks started outside the IBM Systems Director Web interface. Launched tasks useSecure Sockets Layer (SSL), so an exception needs to be granted.

Resolution

For Mozilla Firefox:

84 IBM Systems Director Troubleshooting and Support Guide

Complete the procedure detailed in “Updating the Firefox Web browser to use theJava Web Start program” in the IBM Systems Director Systems Management Guide.

Try the task again. The Opening launch.jnlp message might be displayed. Themessage asks you what you want to do with the .jnlp file. To make sure that thelaunched task can proceed and that this message will not be displayed in thefuture, it is recommended that you select Open with Java Web Start Executableand 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 thetask again.

Java Web Start fails because correct IP address cannot bedetermined

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem

When you try to start a launch-in-context task from IBM Systems Director, the JavaWeb Start - Download Error window is displayed. When you click Details buttonin 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 multipleIP addresses associated with the server, the launch-in-context task might be unableto determine the correct IP address of IBM Systems Director server to use todownload 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: product_install_locationlwi\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.licdirectory.

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 fromwhich 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 multiplecertificates

When attempting to launch any ask that starts outside of the IBM Systems DirectorWeb interface, Java Web Start fails due to JARS signed with multiple certificates.

Troubleshooting and support 85

Problem

After updating to IBM Systems Director version 6.1.2, you might receive an errorwhen running any Launched Tasks using Java Web Start. The error window willcontain the heading Java Web Start - Launch File Error and the message will stateUnable 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 TasksVendor: IBM CorporationCategory: 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 Managerupdate, but do not install the version 6.1.2 System x and BladeCenter Managerupdate. For all code to be signed using the newest RSA Certificate, you mustinstall both manager updates at the same level.

Resolution

To resolve this problem, install the version 6.1.2 System x and BladeCenterManager update, using Update manager.

Launched-tasks feature fails on System z systemThis problem affects System z browser systems.

Problem

When you try to launch a task that starts outside of the IBM Systems Director Webinterface, and your browser system is a System z system, the task fails to launch.

Explanation

Launching tasks that start outside of the IBM Systems Director Web interfacerequires Java Web Start (JWS). However, JWS is not supported on System zoperating systems. Therefore, launching tasks outside of the IBM Systems DirectorWeb interface is not supported on System z operating systems.

Resolution

Change to a browser system that supports JWS to make sure that you have accessto the complete set of IBM Systems Director functions.

Message indicates a failure to validate certificateThis problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

86 IBM Systems Director Troubleshooting and Support Guide

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 rundue to a failure to validate the certificate published by IBM.

Explanation

This message can occur because the SSL certificate published by IBM that was usedto sign files has expired and the Java security settings do not allow users to grantpermission 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 inthe directory path where you installed the Java Runtime Environment(JRE).

For Windows Open Control Panel and click the Java Web Start icon to start JWS.

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 application’s digital signature has an error. Themessage will also indicate that the signature was generated with a trustedcertificate published by IBM, 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 returnyour Java security settings to their original values.

Message indicates that the application’s digital signature hasan error

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

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 digitalsignature has an error. The message further indicates that the digital signature wasgenerated with a trusted certificate published by IBM but has expired or is not yetvalid.

Troubleshooting and support 87

Explanation

These messages can occur because the SSL certificate published by IBM that wasused 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 consolecannot be found

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem

When you try to start a launched task, a message is displayed indicating that IBMSystems Director cannot find an installation image for a console, such as IBMTivoli Storage 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. Formore information, see the configuration instructions for your browser.

v Configure JWS to use the proxy server by completing the followingsteps:

Note: The name of the Java Web Start setting might be slightly differentdepending on the installed version of the Java Runtime Environment(JRE) and the provider. Therefore, the following instructions providegeneral 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 thedirectory 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, continueto step 5 on page 89.

88 IBM Systems Director Troubleshooting and Support Guide

5. Select Use proxy server and specify the address and port for yourproxy server.

For a browser system without direct access to the Internet and does not use aproxy server to access the Internet

IBM Systems Director cannot automatically install the client-based consolesrequired to perform launched tasks. It is recommended that you configurea proxy server to access the Internet. If it is not possible for you to use aproxy server to access the Internet, contact your next level of support oryour service provider.

For detailed information, see “Configuring Web browsers to use Java Web Start.”

Message states that Java Web Start is requiredThis problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem

When you try to start a launched task, a message is displayed indicating that JavaWeb Start (JWS) is required to launch the selected task.

Resolution

Java Web Start (JWS) software is required to launch tasks that start outside of theIBM Systems Director Web interface. If the error message includes a link to a Website, click the link to download JWS. Alternatively, complete the steps in“Downloading Java Web Start” in the IBM Systems Director Systems ManagementGuide.

Multiple Firefox browser windows openThis 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 stepsin Updating the Firefox Web browser to use the Java Web Start program.

Opening launch.jnlp window is displayedThis problem affects the Mozilla Firefox browser.

Problem

When you try to start a launched task, the Opening launch.jnlp window isdisplayed. The message asks you what your browser should do with the file.

Troubleshooting and support 89

Resolution

To resolve this problem, complete one or more of the following actions:v Java Web Start (JWS) software is required to launch tasks that start outside of

the IBM Systems Director Web interface. If the error message includes a link to aWeb site, click the link to download JWS. Alternatively, complete the steps in“Downloading Java Web Start” in the IBM Systems Director Systems ManagementGuide.

v In the Opening launch.jnlp window, click Open with, click Browse, select thejavaws 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, clickEdit.

– 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 informationThese are problems that can occur when you launch an external storageapplication, 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 yoursystem. These applications are not automatically installed with IBM SystemsDirector. See this information center topic for help finding and installing theapplication: Installing and configuring external storage applications.

ATKLIC014W This task requires application name. An earlierversion of application name is installed on this system, but youmust install a later version of application name to complete thetask. To learn about supported software versions and how toinstall them, click Help.

This means that an earlier version of the external storage application is on yoursystem. You must uninstall the earlier version, then install the supported version.

90 IBM Systems Director Troubleshooting and Support Guide

See the Learn More link for the supported versions and other installationinformation.

Storage task unavailable for LSI Integrated RAID ControllerThis problem affects launching the Storage configuration task for an LSI IntegratedRAID Controller when the operating system for the resource to which thecontroller is connected has Common Agent installed.

Problem

After discovering and collecting inventory on a resource to which an LSIIntegrated RAID Controller is attached, the Storage task is unavailable. Forexample, when you right-click the operating system for the resource, the SystemConfiguration > Storage option is not available.

Explanation

The LSI Integrated RAID Controller Storage task is not visible because the installedCommon Agent prevents IBM Systems Director from unlocking the CommonInformation Model (CIM) Remote Service Access Protocol (RSAP) of the operatingsystem. Communicating with the CIM RSAP is required to launch the Storage task.

Resolution

Use the following instructions to make the Storage task visible:1. Remove the Common Agent Services (CAS) RSAP.

a. Right-click the operating system that has Common Agent installed, theselect Security > Configure Access.

b. On the Configure Access page, right-click the entry for CAS, then selectRemove.

2. Unlock the CIM RSAP by successfully requesting access to the same operatingsystem that you targeted in step 1.a. Right-click the operating system, then select Security > Request Access.

Note: After completing the first step, the Request Access selection mighttake a few minutes to become available.

b. Complete the required information, then click Request Access.

Completing this step makes the Storage task selection become available.3. Add and unlock the CAS RSAP.

a. Use System Discovery to discover the same operating system again.b. Unlock the CAS RSAP by successfully requesting access to the operating

system.

Unable to display the requested helpThis problem affects the Mozilla Firefox Web browser.

Problem

When you click Help on a launched-task message to view the help text, thefollowing message is displayed:Unable to display the requested help. Ensure that you specify the path to yourcurrent browser in the Java Web Start settings and click Help again.

Troubleshooting and support 91

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 youinstalled the Java Runtime Environment (JRE).

2. Make sure that you specify the path to your current browser in the JWSsettings.

Note: The name of the Java Web Start setting might be slightly differentdepending on the installed version of the Java Runtime Environment (JRE) andthe provider. For example, Java Web Start might refer to this setting as acommand 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 applicationThis problem affects the Microsoft Internet Explorer and Mozilla Firefox Webbrowsers.

Problem

When you try to start a launched task, one of the following messages is displayed:Unable to launch the application.

orApplication ErrorUnable to launch the application.

orJava Web Start - Invalid Argument ErrorUnable to launch the specified application.

orJava Web Start - Launch File ErrorUnable to launch the specified application.

orJava Web Start - Download ErrorUnable to launch application

orJava Web Start - Launch File ErrorUnable to launch application

where application is the name of the program that failed to launch.

Investigation

In the Application Error window, click Details.

92 IBM Systems Director Troubleshooting and Support Guide

If the More Information window displays the following error message, the problemis caused by an unsupported version of Java Runtime Environment (JRE) and theJRE settings that do not allow IBM Systems Director to download and install thesupported version of the JRE:The application has requested a version of the JRE (version 1.5.0+) that currentlyis not locally installed. Java Web Start is unable to automatically download andinstall the requested version. This JRE must be installed manually.

If the More Information window displays the following error message, the problemis caused by the JRE settings not allowing temporary Internet files to be saved onthe 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 downloadand install the supported version of the JRE.

v (Web browsers running on systems installed with Java version 6.0) Your JREsettings do not allow temporary Internet files to be saved on your computer.

Resolution

To resolve this problem, complete the applicable procedure:

For Internet ExplorerComplete 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 accesssoftware updates for Internet Explorer.

v Click Tools > Internet Options > Advanced. Make sure that Do notsave encrypted pages to disk is not selected.

For a browser system with JRE version 6.0 or later installedComplete the following steps:1. Start the Java Web Start (JWS) application.

For Linux Type javaws at a command prompt. The javaws.exe file is located in thedirectory path where you installed the Java Runtime Environment (JRE).

ForWindows

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. Click the Advanced tab.

Troubleshooting and support 93

7. On the Advanced page, expand JRE Auto-Download.8. Click Prompt User.9. Click OK.

10. Start the affected launched task again. A prompt is displayed todownload the required version of Java.

For a browser system that uses a proxy server to access the InternetComplete 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 differentdepending on the installed version of the Java Runtime Environment(JRE) and the provider. Therefore, the following instructions providegeneral 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 thedirectory 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, continueto step 5 on page 89.

5. Select Use proxy server and specify the address and port for yourproxy server.

For detailed information, see “Configuring Web browsers to use Java WebStart.”

For a browser system without direct access to the Internet and does not use aproxy server to access the Internet

IBM Systems Director cannot automatically install the client-based consolesrequired to perform launched tasks. It is recommended that you configurea proxy server to access the Internet. If it is not possible for you to use aproxy server to access the Internet, contact your next level of support oryour service provider.

For detailed information, see “Configuring Web browsers to use Java WebStart.”

Unable to load resourcesThis problem affects the Microsoft Internet Explorer and Mozilla Firefox browserspointing to a Linux management server.

Problem

When you try to start a launched task, a message is displayed indicating thatresources could not be loaded.

94 IBM Systems Director Troubleshooting and Support Guide

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 themanagement 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 problemresults from the existence of an entry in the /etc/hosts file for the IP address127.0.0.2. This entry results in IBM Systems Director identifying the IP address ofthe affected system as 127.0.0.2. Some IBM Systems Director functions on theaffected managed system and the management server will fail to work asdesigned when this situation occurs.

Note: Using the DNS and host name configuration function of the YAST systemtool 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 LinuxEnterprise Server

In the /etc/hosts file on the affected managed system, comment outthe 127.0.0.2 entry. Insert the pound sign symbol (#) in the firstcharacter 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.

For other Linuxdistributions

Update the final entry in the /etc/hosts file to contain the followinginformation:

v An IP address that can be used to access the management serverfrom 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 CommandsReference.

5. Open the IBM Systems Director Web interface and start the affected launchedtask again.

Troubleshooting and support 95

Windows fails to open a fileThis 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 theprocedure detailed in “Updating the Microsoft Internet Explorer Web browser touse the Java Web Start program” in the IBM Systems Director Systems ManagementGuide.

Accessibility troubleshooting, including JAWSThis section provides information about problems and workarounds foraccessibility and the Freedom Scientific JAWS for Windows screen reader in IBMSystems Director.

Accessible method for installing IBM Systems DirectorUse unattended (silent) install to bypass accessibility limitations ofInstallAnywhere.

Problem

When using the JAWS screen reader, the installation interface is not read in ameaningful order.

Resolution

This problem is a known limitation of InstallAnywhere.

To work around this problem, follow the procedure for Performing an unattendedinstallation of IBM Systems Director Server on Windows.

Note: Silent install does not provide result data when running. After the silentinstall, review the installation log file c:\windows\dirinst.log to verify successfulinstallation or review any error messages.

Preventing session timeouts for users with disabilitiesModify the default session timeout to allow disabled users more time to completetasks.

The IBM Systems Director Server limits the amount of time a browser session canremain inactive before the session is timed out and the user is returned to the loginscreen. To reduce the risk that an abandoned browser session could be accessed byan unauthorized user, the session timeout property may be set to a specific amountof time. The default value of -1 disables session timeout altogether. This property is

96 IBM Systems Director Troubleshooting and Support Guide

a global setting on the IBM Systems Director Server and therefore applies to allbrowser sessions. If disabled users need extended time to work with the interface,an administrator can customize the browser session timeout for all users using thefollowing steps:1. Edit the file <Director-install-directory>\lwi\conf\overrides\

usmi_settings.properties

2. Change the com.ibm.pvc.webcontainer.http.sessionGlobalTimeout propertyvalue to the wanted session timeout in minutes. Example:com.ibm.pvc.webcontainer.http.sessionGlobalTimeout=30

3. Save the usmi_settings.properties file.4. Restart IBM Systems Director Server for the changes to take effect.

Note: This action interrupts all active browser sessions.

Audible notification is not given for wizards in FirefoxThis problem exists in the IBM Systems Director Web interface.

Problem

When using a wizard page, Mozilla Firefox does not play a sound to notify theuser that the page content changed, even when the option to Play sound whendata on the page changes option is enabled after a wizard page loads or displaysmessages.

Resolution

Firefox is the recommended browser for other uses, but wizards are moreaccessible with Internet Explorer for full audio support. Alternatively, the user canre-read the page to verify the page contents. This problem is a known limitation ofIBM Systems Director V6.3 or higher.

Create Virtual Server wizard displays previous page whenpressing Enter in a text field

This problem exists in the Create Virtual Server wizard in the IBM SystemsDirector Web interface.

Problem

In the Create Virtual Server wizard, when you type data in an entry field and thenpress 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 thebottom of the page and press Enter.

Troubleshooting and support 97

Cursor disappears and page refreshes when performingvirtualization manager tasks

This problem affects the IBM Systems Director Web interface when you performvirtualization manager tasks.

Problem

When you perform tasks such as Create Virtual Server, Edit Virtual Server, or EditHost, 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 radiobutton, or browse to select an item in a list. When you select the row, select a radiobutton, or browse through the list, the page refreshes and the cursor seems todisappear. The cursor actually moves to the address bar at the top of the browserwindow; however, you might not be able to see the cursor. Consequently, youmust 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 touse 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 listitem by pressing Alt and the Down Arrow key.

Focus is lost when clicking the Select All or Deselect Allbutton

This problem exists in virtualization manager the IBM Systems Director Webinterface.

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. Thisoccurs in the Edit Virtual Resources page.

Resolution

When the page refreshes, focus moves to the top of the page. Navigate back to thedesired location on the page.

Identifying table filter row information using JAWSThis problem exists in the IBM Systems Director Web interface. The table summaryidentifier shown when issuing a list tables command in JAWS with table filter rowenabled shows two tables with similar summaries.

Problem

One of the features of the tables used in the IBM Systems Director Web interface isto allow for filtering of the data contained in the rows of a given table. The featureis enabled by selecting Show filter row in the Action menu. When using JAWS tolist the tables on a page after enabling the filter row functionality, two tables arelisted with similar tables summaries. The table identified as having two rows afterenabling filter row capability is the filter control table for the main table.

98 IBM Systems Director Troubleshooting and Support Guide

Examples

If you select the Resource Explorer link in the console navigation and then selectthe All Operating Systems resources link, if you issue the JAWS list tablescommand, the JAWS dialog lists one table with the summary "This table containsthe resources found in the 'All Operating Systems' data set 9x6". If you select Showfilter row from the Actions button menu and then issue the JAWS show all tablescommand, 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 'AllOperating Systems' data set 9x2". This second two-row table contains the filter rowcontrol for the first table and can be used to define filters to filter the data in themain table.

Resolution

Use the second table which contains the filter row control to filter the main table.

JAWS screen reader becomes muteThis problem exists only in the Create Simple Event Filter page in the IBM SystemsDirector Web interface.

Problem

When using the JAWS screen reader with the Java Access Bridge and the JavaConsole, if you clear the Any check box in the Event Type page, JAWS becomesmute and several keys on the keyboard are frozen, which causes the Web interfaceto 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 Webinterface, but do not reattempt the above function

JAWS does not read Pre-Installation Utility contentThis problem exists in the IBM Systems Director Pre-Installation Utility.

Problem

When using the IBM Systems Director Pre-Installation Utility to install IBMSystems Director with JAWS screen reader, the frames are read but the pagecontent 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 meaningfulorder. See related topic Accessible method for installing IBM Systems Director formore information.

Troubleshooting and support 99

JAWS screen reader reads extra frameThis problem exists in the IBM Systems Director Web interface.

Problem

In the Remote Command Line page, if you request the list of frames in the pageand then navigate to frames in the list using the M key, the screen reader reads theextra views frame at the end of the list. This also happens when using the WindowEyes screen reader.

Resolution

Ignore the extra views frame when it is read.

JAWS cannot read remote serial console outputThis problem inhibits use of Remote Access Serial Console with JAWS.

Problem

If you select a CEC server and launch the Remote Access Serial Console, JAWScannot read the console content. An alternate method of access is required toenable 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: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/dp’with DISPLAY=window

julie04: Launching serial console window

4. From the management server command line, type the dconsole command withthe -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 tothe specified target in the previous step. JAWS can read the input and outputgenerated in the Windows command prompt window.

JAWS screen reader reads some Web interface elementsincorrectly

This problem exists in the IBM Systems Director Web interface.

100 IBM Systems Director Troubleshooting and Support Guide

Problem

When using the JAWS screen reader the following Web interface elements mightnot 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 anavigational signpost. The breadcrumb link for the current page might be readincorrectly.

v Required fields in the Console Logging and Tracing page might not be readcorrectly.

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 NavigationPreferences window. Instead, the Name column in the header row is readrepeatedly.

v The radio button group text in the Create Virtual Server Image page is not beingread, 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 younavigate to each step in the wizard, the name of the current step is readcorrectly.

v The label of the icon before an error message is not read, even if the Enabletables 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 Plug-ins tab on theHome page, a new page is displayed. When using the JAWS screen reader, linkson the to the summary pages are read as if the summary pages are in the samepage.

v Hidden frames with their invisible elements (such as invisible buttons) are beingread. For example, if multiple tabs are open, only the current tab is visible in thebrowser, but JAWs reads the inactive tabs as well as the active tab.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 labeldescriptions, 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 includethe radio button group text.

Troubleshooting and support 101

JAWS screen reader suggests incorrect keys for radio buttonsin 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 radiobutton selection for radio buttons embedded in a table.

Problem

When using the JAWS screen reader, depending on the verbosity setting, JAWSmay direct the user to use the arrow keys to change the state of radio buttonsembedded in certain tables for table row selection, but the arrow keys do not workto change the state of the radio button. Use the enter key or space key (dependingon their JAWS Keyboard Manager settings) to change the state of such a selectedradio button.

Resolution

Use the space bar or enter key to change the radio button selection state instead ofthe arrow keys as possibly directed by Director.

JAWS screen reader reads the Next button incorrectly onsome pages

This problem exists in the IBM Systems Director Web interface.

Problem

When using IBM Systems Director wizards in Internet Explorer, if you enter datain a text field (in other words, if you type data and then press Enter), the Nextbutton 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 wizardthen press Enter to advance to the next panel.

Keyboard navigation does not work in or between Selectedand Available list boxes

This problem exists in virtualization manager the IBM Systems Director Webinterface.

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 beforesubmitting a task.

102 IBM Systems Director Troubleshooting and Support Guide

v Keyboard navigation does not work when moving from Selected list box back tothe Available list box after removing items from the Selected list box in the DiskSelection page of the Create Virtual Server wizard. The focus goes to the Addbutton 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 thatexplains how the dialog works.

v After the focus goes to the Add button, press Shift-Tab to put focus on theAvailable list.

Keyboard navigation does not work in some Action menusThis problem exists in the IBM Systems Director Web interface.

Problem

When using the JAWS screen reader, the Actions menu cannot be traversed usingarrow keys keyboard in the Create Virtual Server wizard - Disk Selection page andthe 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 whenusing Internet Explorer

This problem exists in the IBM Systems Director Web interface.

Problem

The LANG attribute of the HTML element determines which language assistivetechnologies, such as Braille software and screen readers, to use to correctlypronounce the text. The LANG attribute is set properly when using the Firefox, butit is not set correctly in some pages when using the Internet Explorer.

Multiple read-only input text areas in same page are readincorrectly by JAWS in Firefox

This problem exists in the IBM Systems Director Web interface, often in theSummary step of a wizard.

Troubleshooting and support 103

Problem

In Mozilla Firefox, when there are more than one text area in the same pagemarked as read-only, JAWS screen reader cannot read them all correctly. Sometimesit reads the text twice, sometimes it skips text. It may also recognize the text as"read-only edit" or "edit".

Note: This function works correctly in Internet Explorer.

Resolution

Use JAWS to re-read the page to verify the content in Internet Explorer. Thisproblem is a known limitation of IBM Systems Director 6.3.x or higher.

The calendar is not usable or readable by the JAWS screenreader in forms mode

This problem affects the Launch Job window in the IBM Systems Director Webinterface.

Problem

In the Launch Job window, on the Schedule page, the calendar is not usable orreadable by the JAWS screen reader in forms mode with any supported Webbrowser.

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 monthv dd is the two-digit day of the monthv 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 readerThis problem affects the Launch Job window in the IBM Systems Director Webinterface.

Problem

In the Launch Job window, on its Schedule page, the Time field is not readable bythe JAWS screen reader with any supported Web browser.

Resolution

To resolve this problem, complete the following steps:1. Navigate to the Time field2. 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.

104 IBM Systems Director Troubleshooting and Support Guide

Unable to navigate to expanded content with traditional keysequences when using JAWS screen reader

(IBM Systems Director 6.1 only) This problem exists in the RSSM/NSSM Portspanel in the IBM Systems Director Web interface. This problem is resolved in IBMSystems Director version 6.1.1.

Problem

When using the JAWS screen reader, the traditional JAWS key sequences do notnavigate to the expanded content in the Blade Bay Ports and External SAS Portssections on the RSSM/NSSM Ports panel. JAWS does not say the names of checkboxes and associated text when using the Tab key, forms keystrokes orInsert+down arrow keys to reach this area.

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 arrowkey combinations to read one word at a time.

Automation manager troubleshootingThis section provides information about problems and workarounds for theautomation manager plug-in.

A program fails to run when the event automation plans istriggered

This problem affects event automation plans that include either of the followingevent actions: Start a program on a system or Start a program on the systemthat generated the event.

Problem

When creating either of the following event actions, you specify a program to runwhen the event action is invoked:v Start a program on a systemv Start a program on the system that generated the event

However, the program might not run after the event occurs that triggers thisaction.

Explanation

These two types of the event actions are used to run a program to complete somesystems-management tasks on a remote system when an event occurs. However,the program must be an executable and IBM Systems Director must be able toaccess and manage the affected system.

Resolution

To resolve this problem, complete the following steps:

Troubleshooting and support 105

1. If the event action history was activated, check to make sure the event actionwas launched. For more information, see “Activating and deactivating anevent-action history” and “Viewing an event-action history.”

2. Make sure the selected protocol for the event action is correct. If the specifiedsystem is running Common Agent, the selected protocol must be CAS. If thespecified system is running IBM Director Agent version 5.20, the selectedprotocol 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 toaccess Common Agent. If not, request access to the system. For moreinformation, see “Requesting access to a secured system.”

5. On system specified, make sure that the com.ibm.usmi.client.ipc_1.0.0 plug-inwas installed successfully in the install_root/agent/runtime/agent/subagents/eclipse/plugins/ directory where install_root is the root directory of your IBMSystems Director installation. Note that this path uses the backslash (\) todelimit the directory; depending on the system that you are using, you mightbe required to enter the path using the forward slash (/).

Active Energy Manager threshold options are not displayed inthe Event Automation Plan wizard

This problem affects the Event Automation Plan wizard after you have installedthe Active Energy Manager plug-in.

Problem

After you install the Active Energy Manager plug-in, additional threshold optionsshould become available in the Event Automation Plan wizard; however, they donot.

Explanation

The Active Energy Manager license has expired or the Active Energy Managerplug-in is not installing correctly.

Resolution

Check the license agreement and make sure that the Active Energy Managerplug-in was installed successfully.

The specified event does not trigger the event automationplan

This problem affects event automation plans.

Problem

An event automation plan specifies an event for monitoring. However, when theevent 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.

106 IBM Systems Director Troubleshooting and Support Guide

v The event filter no longer exists.

Investigation

Make sure that the event automation plan is activated. On the Event AutomationPlans 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 displayedon the Event Filters page.

Note: If the event automation plan was created using the Event Automation Planwizard 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 eventautomation plan.

2. Click Actions > Activate.

Missing event filter

1. On the Event Automation Plans page, select the affected eventautomation 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 eventautomation 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 eventfilter uses extended details

This problem affects event automation plans that include an event filter that usesextended details. While this problem can affect any event filter that uses extendeddetails, this resolution provides information that is specific to message events fromIBM i systems.

Problem

An event automation plan with an event filter that uses extended details might nottrigger as expected. Many individual event types have extended details. For moreinformation about extended details, see “Events.”

Troubleshooting and support 107

Investigation

IBM i message events, like other event types, have extended details that arespecific to the event type. The keywords to operate on are listed but the valuesthat are applicable to those keywords are usually not listed. The values can befound external to IBM Systems Director.

Make sure that the logical OR and logical AND (as described in the help) thatapply to the selected keyword or keywords works for the intended inclusion orexclusion of the event.

Explanation

Values for extended details are found outside IBM Systems Director. Event filtersusing extended details that have multiple values for the same keyword use logicalOR, but multiple keywords use logical AND.

Resolution

To avoid having an event automation plan fail to trigger after changing the eventfilter with extended details, make sure the logic for the filtering of events is correctin the following situations:v When using logical OR on multiple values of the same keywordv When using logical AND on multiple keywords

Additional information

IBM i message events have several keywords listed such as Message type andMessage severity. The following table lists the possible values and meanings forthe Message type keyword.

Table 3. Possible values and meanings for the Message type keyword

Value Message Type

01 Completion

02 Diagnostic

04 Informational

05 Inquiry

06 Sender's copy

08 Request

10 Request with prompting

14 Notify, exception already handled

15 Escape, exception already handled

16 Notify, exception not handled

17 Escape, exception not handled

21 Reply, not checked for validity

22 Reply, checked for validity

23 Reply, message default used

24 Reply, system default used

25 Reply, from system reply list

26 Reply, from exit program

108 IBM Systems Director Troubleshooting and Support Guide

The Message severity is the value of the severity code which is a number from 0 to99. The Message severity is much like the severity of a message on the Severitypage in the Event Filter Builder window, except on the Severity page the severityis a mapping of the number to a keyword.

SeverityIBM SystemsDirector maps the message event severity as followsif msg severity < 10 then HARMLESSelse msg severity < 20 then WARNINGelse msg severity < 30 then MINORelse msg severity < 80 then CRITICALelse msg severity is FATAL

An SNMP trap or an SNMP inform request was not receivedThis problem affects event automation plans that include any of the followingevent actions: Send an SNMP INFORM request to an IP host, Send an SNMP trapreliably 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 notreceived by the SNMP program:v Send an SNMP INFORM request to an IP hostv Send an SNMP trap reliably to a NetView hostv Send an SNMP trap to an IP host

Explanation

These types of the event actions are used to send an SNMP trap or SNMP informto an SNMP program. SNMP notifications can be sent out as a trap or an informrequest. Traps are unreliable notification because the receiver does not reply to thesender after it receives the traps. However, the inform requests are reliable becausethe receiver sends an acknowledgement to the sender after receiving the informrequest. To receive SNMP traps or inform requests, the SNMP program must beconfigured correctly.

Note: An SNMP program that can receive traps does not mean that it can receiveinform requests.

Resolution

Configure the SNMP program correctly. For more information, see the SNMPprogram documentation.

Note: There is no configuration required for IBM Systems Director Server to sendan SNMP trap or inform request.

Automation plan not activated for virtual farm or relocationevent

This problem can affect several virtualization environments.

Troubleshooting and support 109

Problem

An automation plan that uses a virtual farm event filter or relocation event filterdoes not get activated as expected when the specified event occurs and displays inthe 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 mightbe experiencing a problem with your automation plan if you have specified anevent type path that is not associated with the virtualization environment wherethe event is occurring.

v You might not have applied the automation plan to a valid target system for theevent type that you plan to filter.

Resolution

Ensure that the event type that you have specified in your automation plan usesthe appropriate path for your specific virtualization environment. The followingtable displays the paths to specify for event types in different virtualizationenvironments.

CategoryPath in EventFilter Builder Event Types

VMwareVirtualCenter

VMwareESX Server

HMCor IVM

Virtual farmfilters

Managed Resource> Managed SystemResource > LogicalResource > System> AdministrationDomain > Farm >Life Cycle

v A virtual farm has beencreated.

v A virtual farm has beendeleted.

v A virtual farm has beenrenamed.

v A host was added to avirtual farm.

v A host was removed from avirtual farm.

X

Managed Resource> Managed SystemResource > LogicalResource > System> AdministrationDomain > Farm >Virtual FarmEvents

v Virtual farm created

v Host added to virtual farm

v Host removed from virtualfarm

v Virtual farm renamed

X X

110 IBM Systems Director Troubleshooting and Support Guide

CategoryPath in EventFilter Builder Event Types

VMwareVirtualCenter

VMwareESX Server

HMCor IVM

Relocationfilters

Managed Resource> Managed SystemResource > LogicalResource > System> ComputerSystem > Server >Relocation

v Virtual server relocation hasbeen initiated for {0}.

v Virtual server relocation hascompleted.

X X

Managed Resource> Managed SystemResource > LogicalResource > System> AdministrationDomain > Farm >Relocation ManagerEvents

v Virtual server relocationstarted

v Virtual Server relocationfailed

v Virtual server relocationcomplete

X

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 forthe automation plan. For relocation events, ensure that you select the target hostfor relocation as the target system for the automation plan.

Cannot run Collect Inventory task using an event action(IBM Systems Director 6.1 only) This problem affects the event action Start a taskon the system that generated the event. This problem is resolved in IBM SystemsDirector version 6.1.1.

Problem

When you create a Start a task on the system that generated the event event actionand select to start the Collect Inventory task, the task fails to run when the eventaction is invoked.

Explanation

The Collect Inventory task provided in the Start a task on the system thatgenerated the event event action window does not work in IBM Systems Director6.1.

Resolution

To resolve this problem, use the event action Start a task on a specified system toinvoke the Collect Inventory task.

Difficulty accessing event automation plan system variablesThis problem affects an event automation plan that specifies the Set an eventsystem variable event action.

Problem

When using the Set an event system variable event action, the system variable isnot accessible from scripts and other system tools.

Troubleshooting and support 111

Investigation

The Set an event system variable event action is used to set the value of auser-defined variable. After the action is invoked, the variable and its value are notvisible as operating-system environment variables.

Note: The Set an event system variable event action is used to set the value of auser-defined event system variable, not operating-system variables.

Explanation

The system variables used by the Set an event system variable event action areintended for use only in event automation plans. The variables and their valuescan be used only in an advanced event filter to further refine the conditions forthat filter. When creating an advanced event filter, in the Event Filter Builder, viewthe System Variables page. On this page you can specify the values of the systemvariables.

E-mail fails to be sentThis problem affects event automation plans that include either of the followingevent actions: Send an e-mail to a mobile phone or Send an e-mail (InternetSMTP) .

Problem

When using either of the following event actions, the e-mail fails to be sent:v Send an e-mail to a mobile phonev Send an e-mail (Internet SMTP)

When you test these actions, you might receive the error message Action launchfailed.

Explanation

These actions only work when the management server can reach the SMTP server.Additionally, IBM Systems Director Server does not support SMTP serverauthentication. Therefore, the SMTP e-mail server must be configured to receivee-mails without a user name and password.

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 Change the SMTP server configuration to receive e-mails from IBM Systems

Director Server without authentication.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 themanagement server. If the ping fails, a connection issue exists between themanagement server and the SMTP server. If ICMP traffic is disabled, considerusing ssh or Telnet to confirm that the servers can communicate successfully.

v If applicable, check your firewall settings and access. Consider checking othernetwork-related settings, too.

112 IBM Systems Director Troubleshooting and Support Guide

Event actions failThis 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 werediscovered before the configuration change.

Resolution

To resolve this problem, you must rediscover the affected resources. In the Webinterface navigation pane, expand Inventory and click System Discovery. For moreinformation, see “Performing a system discovery.”

Target systems are lost when an event automation plan isimported

This problem affects all hardware and operating system platforms.

Problem

You export an event automation plan from one IBM Systems Director managementserver (the server running IBM Systems Director Server) and import the eventautomation plan to a different management server. When you open the importedevent automation plan, the target systems are missing in the event automationplan.

Explanation

This behavior occurs when an event automation plan is exported from one IBMSystems Director management server and imported on a different managementserver. This behavior also occurs when using earlier versions of IBM Director. Thisis working as designed.

Previously, each target system had an object ID (OID) generated by themanagement server. It was possible that two management servers could generatethe same OID, but for two different systems. In that case, the imported target OIDwould be for a different target system than on the exporting management server.

To address this, IBM Systems Director was changed to generate a globally uniqueID (GUID). The GUID lets the import code detect whether the exported targetsystems 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 bothmanagement servers. In this case, the target systems are deleted from the importedplan. If the deletion is not done, the imported plan could erroneously be applied toa different set of target systems than you originally specified.

Resolution

After the event automation plan has been imported onto a different IBM SystemsDirector management server, edit the event automation plan and select the desired

Troubleshooting and support 113

target systems as they are known to the import management server.

Event automation plans are not displayedThis problem affects viewing event automation plans that affect a system.

Problem

When you view the Applied Activities page in the Properties view, one or moreevent automation plans that affect the selected system are not displayed.

Explanation

When you apply an event automation plan to a group, the event automation planis associated with all existing systems in the group. However, this group eventautomation plan is not displayed as associated with each individual system that isa member of the group. The event automation plan is displayed as being appliedto the group only.

Resolution

In order to determine whether a group-applied event automation plan affects anindividual system, you must know to what groups a system belongs. While youcan navigate to a group and view its members in the IBM Systems Director Webinterface, you cannot view a resource and determine of what groups it is amember. 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.”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 aspecific system. For more information, see “lsevtautopln command.”

Event automation plans do not support some features ofearlier event action plans

An event automation plan might not provide the same features as an event actionplan 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 planmight not be permitted in an event automation plan if the event filters areAdvanced event filters or the event actions are not applicable to the IBM SystemsDirector Web interface.

Investigation

In earlier releases, event action plans could use multiple event filters and multipleevent actions. In an event automation plan, only one event filter is supported, theevent filter can be one advanced event filter or one common filter for the plan thatcontains one or more event types.

Some event actions from earlier releases are no longer available.

114 IBM Systems Director Troubleshooting and Support Guide

Explanation

The event action plans used in the past might require multiple event automationplans to provide the same coverage and the event actions might need to bedifferent.

Resolution

When needed, create multiple event automation plans to cover all the advancedevent filters that were in an event action plan. If the event action used in an eventaction plan no longer exists, choose a different action for your event automationplans.

Event automation plans do not work correctlyThis problem affects event automation plans that reside on management serversrunning Windows.

Problem

Event automation plans do not work or have unpredictable results.

Explanation

Daylight savings time can affect event automation plans on days when daylightsavings time starts or ends. On days when daylight savings time starts, eventautomation plans that are scheduled during the hour when the management serverclock skips forward might not run. On days when daylight savings time ends,event automation plans that are scheduled during the hour before the managementserver clock falls back might run twice.

Resolution

To prevent this problem, do not schedule event automation plans during thesetimes if you are in a locality that observes daylight savings time.

Event not forwarded to Tivoli Enterprise Console event serverThis problem affects the event action that forwards events from IBM SystemsDirector Server to a Tivoli Enterprise Console® event server.

Problem

The event action called “Send a Tivoli Enterprise Console event” does not forwardsome events successfully to a Tivoli Enterprise Console event server.

Explanation

When a detected event triggers the event action called “Send a Tivoli EnterpriseConsole event”, IBM Systems Director retrieves data from the incoming event andcreates a packet of data to forward (transmit). The packet of data includes thesystem name (as it appears in the IBM Systems Director Web interface) thatinitiated the event. When the system name includes a pound (#) character orexclamation point (!) character, Tivoli Enterprise Console event server rejects thetransmission.

Troubleshooting and support 115

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 groupsThis problem affects event automation plans that include either of the followingevent actions: Static group: add or remove the event-generating system orStatic group: add or remove group members.

Problem

When creating either of the following event actions, the members are not added tothe target group or removed from the target group, as applicable:v Static group: add or remove the event-generating systemv Static group: add or remove group members

Explanation

These two event actions are used to process static groups only. Therefore, both thesource group and the target group must be static groups. The members of thestatic group must be managed systems and the member cannot be a nested groupitself.

Resolution

Make sure that the source group and target group are static groups. Also, makesure that the members in the source group are managed systems.

IBM i message queue events do not trigger event automationplans as expected

This problem affects event automation plans that include an event filter for IBM imessage queue events.

Problem

An event automation plan does not deliver the expected results for IBM i messagequeue events.

Investigation

By default, IBM i message queue events are not included in the Event FilterBuilder. For IBM i message queue events to be filtered, you must specify themexplicitly.

Explanation

If you have configured your event automation plan to trigger IBM i message queueevents, complete the following steps to verify that the event automation plan isconfigured 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

116 IBM Systems Director Troubleshooting and Support Guide

Systems Director Systems Management Guide. Verify that you have included eachmessage queue event that you want to monitor and that the spelling andsyntax is correct.

2. If you are using the exclusion event filter, verify that message queue events arenot 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 worktogether 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 isinvoked.

4. Check that the event automation plan is applied correctly to the systems thatyou want to monitor.

5. Make sure that any firewall configuration allows access in and out of thesystems 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. Forexample, you can create a CL program and use QSYS/SNDPGMMSG in theCL program to send a message to the managed system. For moreinformation, see “Commands used to send messages from a CL program.”

b. Manually verify that the message arrived at the message queue on themanaged system by using the QSYS/DSPMSG command.

Resolution

Verify that the following items as described in the Investigation section areconfigured 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.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 amessage queue event and invoke an event action as described in the plan. Ifproblems persist, contact your IBM service representative.Related information:

Commands used to send messages from a CL program

News fails to post to a newsgroupThis 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 notposted on the news server.

Explanation

This action can only send news to a newsgroup that does not require user login.

Troubleshooting and support 117

Resolution

Make sure that the newsgroup does not require a user login.

Resource-monitor threshold settings change unexpectedlyThis problem affects event automation plans that use resource-monitor thresholdsettings.

Problem

A resource-monitor threshold setting that you specified in an event automationplan, changed from the value you specified unexpectedly. When the value ischanged, 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 atany 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 followingresource-monitor threshold setting: Processor (CPU) resource threshold at 90%on moonlite

The Processor (CPU) resource threshold setting in event automation plan 1 ischanged to 90%.

When working with resource-monitors and event automation plans, remember thefollowing considerations: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 yourfirst event automation plan. You cannot have second event automation plan thatmonitors the Processor (CPU) resource threshold at 80% on moonlite. If you docreate another event automation plan with a different threshold setting, then thatsetting is also used in the first event automation plan and any other eventautomation plans that monitor the Processor (CPU) resource on moonlite.

v For a given system, you can monitor more than one type of resource. Forexample, you can have one event automation plan that monitors the Processor(CPU) resource threshold at 80% on moonlite and another event automation planthat monitors the Disk resource threshold of 70% on moonlite.

v You can combine more than one resource monitor threshold setting in an eventautomation plan as long as the resources being monitored are different. Forexample, you can specify the following resource-monitor thresholds in one eventautomation plan:– The Processor (CPU) resource threshold at 80% on moonlite– The Disk resource threshold of 70% on moonlite

SNMP traps do not contain message textThis problem affects IBM Systems Director Server.

118 IBM Systems Director Troubleshooting and Support Guide

Problem

SNMP traps received from Platform Agent, Common Agent, or IBM Director CoreServices 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 IBMSystems 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 IBM-SYSTEM-NETWORK-MIB.mib

v IBM-SYSTEM-POWER-MIB.mib

v IBM-SYSTEM-PROCESSOR-MIB.mib

v IBM-SYSTEM-RAID-MIB.mib

v IBM-SYSTEM-SMART-MIB.mib

v IBM-SYSTEM-STORAGE-MIB.mib

These MIB files are located in the following directory:v AIX or Linux: /opt/ibm/icc/proddata/snmp

v Windows: \Program Files\Common Files\IBM\icc\proddata\snmp

Start a program on a system event action failsThis problems affects event automation plans that include the Start a program ona system event action.

Problem

When an event automation plan invokes the Start a program on a system eventaction, the event action completion status is reported as Failed.

Explanation

This failure might be due to selecting an incorrect protocol when creating the eventaction.

IBM Systems Director 6.1 or later supports the following managed systems:v IBM Systems Director Server 6.1 or later and Common Agentv IBM Director Server, version 5.20 and IBM Director Agent, version 5.20

Troubleshooting and support 119

IBM Systems Director 6.1 or later uses Tivoli Common Agent Services (CAS) tocommunicate between the management server and managed systems. IBMDirector, version 5.20, uses TCP/IP to communicate between management serverand managed systems. Because the protocols used for communication are changed,you must select a different protocol when creating the Start a program on asystem event action, depending on the product versions that are installed on theaffected management server and managed systems.

Resolution

When you create a Start a program on a system event action, select the applicableprotocol depending on the version of the product installed on the target system.

Product version installed on the targetsystem Protocol to select

IBM Systems Director Server 6.1 or later, andCommon Agent

CAS

IBM Director Server 5.20, and IBM DirectorAgent 5.20

TCP/IP

Test results are missing for an event actionThis 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 testthe action before using it in an event automation plan. However, when you do testthe 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. Bydefault, the event-action history for each action is disabled. You can enable thehistory either on the Event Actions page or using the command-line interface. TheHistory column in the table on the Event Actions page indicates whether thehistory is enabled for each action. If the history is disabled, you can enable it byselecting the action and then clicking Actions > Enable History.

After the event-action history is enabled for an action, the results of that action arelogged when it is invoked from an event automation plan or when you test theaction from the Event Actions page.

Note: If you test an action from the Event Automation Plan wizard, the results ofthat 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 alsocompleted successfully.

Also, when creating or editing certain types of event actions, a Test button isavailable to test the action. The testing of the action in the Create or Edit windowdoes not capture the test result, it only indicates whether the event action waslaunched successfully. To verify that the action successfully completed, you must

120 IBM Systems Director Troubleshooting and Support Guide

check the action's outcome. For example, if you created an e-mail action, checkyour 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. Selectthe action and then click Actions > Enable History.

Threshold values are no longer selected or are zeroed out inan event automation plan

This problem affects event automation plans that were created in the EventAutomation 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 Statusand Health. If you delete the threshold in the Thresholds task, then the eventautomation plan still contains the event type of the threshold but the values are nolonger selected or are zeroed out.

Resolution

To correct the threshold event automation plan, you must edit the eventautomation plan and set the threshold values again. Then, save the eventautomation plan.

Unfamiliar event filters are displayed on the Event Filters pageThis problem affects event automation plans that were created in the EventAutomation Plan wizard.

Problem

The Event Filters page displays unfamiliar event filters.

Explanation

When you select a Common event type when using the Event Automation Planwizard, an event filter is created that represents the selected event types. Youcannot edit this event filter because the associated event automation plan isdependent upon it.

Note: The filter name is plan_name-Filter, where plan_name is the event automationplan name.

Resolution

If the event automation plan is deleted, the event filter is deleted automatically.

Configuration manager troubleshootingThis section provides information about problems and workarounds for theconfiguration manager plug-in.

Troubleshooting and support 121

Configuration manager status is shown as Not Ready in theHome page

Configuration manager functions are not available.

Problem

The Plug-ins tab of the IBM Systems Director Home page shows the status ofConfiguration Manager as Not ready. The configuration manager server, editor, ortheir dependent services might not be available. Also, attempts to use any of theconfiguration manager functions will result in the error message: ATKCOR031E Anunknown 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 IBM BladeCenter and System x interface (com.ibm.director.bcxconfigmanager)v Storage interface (com.ibm.director.storconfigmanager)v CIM Client Factory service (com.ibm.usmi.client.cim.sblimimpl)v Client service (com.ibm.usmi.client.services)v Event Router service (com.ibm.usmi.kernel.USMIKernelv Manageable Element service (com.ibm.usmi.kernel.USMIKernel)v 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)

Explanation

Configuration manager functions are built on some of the core services available inIBM Systems Director Server. The configuration manager framework waits for allthe dependent services be available before starting.

The core services that Configuration Manager depends on are:v Chassis Information servicev CIM Client Factory servicev Client servicev Event Router servicev Manageable Element servicev Persistence servicev Task servicev Template service

If any of these services are not available, the configuration manager functions arealso not available.

On AIX and Linux systems, use this command to list all the installed bundles withtheir status. This command directs the output to a file named output_file.txt.

122 IBM Systems Director Troubleshooting and Support Guide

lwiplugin.sh -status > output_file.txt

On Windows systems, use this command to list all the installed bundles with theirstatus. 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 notACTIVE, then try to manually start them. This command can be used to start abundle 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 SystemsDirector home directory.

If the manual start of the dependent bundles do not change the ConfigurationManager availability status to Ready, and if the IBM Systems Director Server wasinstalled using ISDServerSetup.exe (on the Windows platform), then contact yourservice provider. If the IBM Systems Director Server was not installed usingISDServerSetup.exe (on the Windows platform), then uninstall the IBM SystemsDirector Server and reinstall it using this install program.

Mass configuration fails to configure Asset ID informationThis problem affects mass configuration and Asset ID configuration in theConfiguration Manager task.

Problem

In the Configuration Manager task, when you use mass configuration and theAsset ID configuration template to configure Asset ID information, theconfiguration fails.

Explanation

The affected system does not have sufficient data space. When the size of theconfiguration 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 ofthe data save area.

When in deferred mode, the template cannot determine the amount of data spaceon the system and uses 1024 bytes as a default amount. If the input exceeds 1024bytes, the template prevents the configuration from being saved and the Deploybutton is disabled. When the template is applied to a target system, the amount ofactual 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 thefollowing ways:

Troubleshooting and support 123

v In the activation log. In the Configuration Templates table, select the templateand then click Actions > Properties. In the Properties view, click the Logs tab.On the Logs page, select the job activation record. The activation log isdisplayed below the table.

v In the install_root/log/configmgrplugin.log file, where install_root is the rootdirectory of your IBM Systems Director installation. Note that this path uses thebackslash (\) to delimit the directory; depending on the system that you areusing, you might be required to enter the path using the forward slash (/).

When in immediate mode, the template determines the amount of data space onthe target system. If the input exceeds the amount of available data space, thetemplate prevents the configuration from being saved and the Deploy button isdisabled.

Resolution

Make sure that the total bytes of data that you input does not exceed themaximum number of bytes that the data space can save on the managed resource.

Deploy of a configuration template fails on a target device thatis not supported

This problem affects all areas that use configuration templates. A deploy task couldhang 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 thatconfiguration template does not support, then you check progress of the deployjob, you will find that there is no progress bar displayed on the scheduled jobproperties page and its status is 'Active'.

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 ofthe 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.

124 IBM Systems Director Troubleshooting and Support Guide

Discovery manager (including inventory) troubleshootingThis section provides information for specific problems and workaroundsassociated with discovery and inventory in the IBM Systems Director environment.

Discovery troubleshootingThis section provides information for specific problems and workaroundsassociated with the Discovery task.

A Platform Agent managed system running VMware 3.5 isdiscovered as an agentless managed systemThis limitation affects Platform Agent managed systems running VMware ESX 3.5update 3.

Problem

After installing Platform Agent on a managed system running VMware ESX 3.5update 3, the managed system appears in IBM Systems Director Web interface asan 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 Webinterface.

v OpenPegasus is restarted on the managed system after installing Platform Agentbut before adding and gaining access to the managed system in IBM SystemsDirector Web interface.

Explanation

This problem occurs because the version of OpenPegasus that is included withVMware ESX 3.5 update 3 has a built-in SLP service agent. When OpenPegasusstarts, it takes control of port 427, removing the registration for the Platform Agentservice agent.

Resolution

To resolve this problem after the managed system is rebooted or afterOpenPegasus 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 managedsystem running VMware ESX 3.5 update 2 or update 3.

After a PPMO is deleted, it reappears in IBM Systems DirectorWeb interfaceThis problem affects IBM Systems Director Web interface.

Problem

After a physical platform managed resource is deleted, it reappears in IBMSystems Director Web interface.

Troubleshooting and support 125

Investigation

Delete the managed resource or systems that are associated with the physicalplatform managed resource.

Allow time before discovery of a new switchThis problem affects users who discover, request access or remove switches usingscripts.

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 ofdiscovery.

Automatically requesting access to a previously discoveredresource failsThis problem affects discoveries that use a discovery profile to automaticallyrequest access to one or more previously discovered resources.

Problem

When a discovery automatically requests access to a previously discoveredresource to which IBM Systems Director currently does not have access, the accessrequest fails. After the discovery process finishes running, the previouslydiscovered resource to which IBM Systems Director did not have access still has astatus of No Access. When the discovery process cannot access a resource, theprocess also cannot collect inventory for that resource.

Explanation

Automatically requesting access applies only to resources discovered during thecurrent discovery process. If a resource was discovered previously, the currentdiscovery process retrieves existing information for that resource from the IBMSystems Director Server. Because the resource was discovered previously, thecurrent discovery does not discover the resource, does not request access to theresource, and does not indicate an error.

Resolution

Remove the previously discovered resource to which you want to automaticallyrequest access. After removing the specified resource, running the discovery againsuccessfully requests access to the resource.

Cannot add a management module or Remote SupervisorAdapter II to IBM Systems DirectorThis problem affects the IBM BladeCenter management module, advancedmanagement module, and Remote Supervisor Adapter II.

126 IBM Systems Director Troubleshooting and Support Guide

Problem

When you add an IBM BladeCenter management module, advanced managementmodule, or a Remote Supervisor Adapter II to IBM Systems Director, either of thefollowing errors is displayed: Cannot Add BladeCenter Chassis or Cannot adddevice.

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 SupervisorAdapter II.

4. Repeat the process to add the affected management module or RemoteSupervisor Adapter II to IBM Systems Director.

Cannot add a Windows 2003 system as an SNMP deviceThis problem affects SNMP-managed resources running Windows 2003.

Problem

Even if the SNMP service is installed and running, a Windows 2003 system cannotbe 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.3. Double-click Services.4. Right-click SNMP Service and select Properties.5. In the SNMP Service Properties window, click the Security page.6. In Accepted Community Names group, click Add.7. 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 yourmanagement server in the Accept SNMP Packets from these hosts area.

Cannot discover agent properly on managed systemThis problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem:

After you modify the IP address of a platform agent through the IBM SystemsDirector network configuration plug-in, rediscovering the platform agent throughits new IP address interrupts CIM access.

Explanation:

Troubleshooting and support 127

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 theseservices by running the listed commands in the order given.

Note: After restarting, it takes approximately 3-5 minutes before your system isfully started.v Linux

/etc/init.d/cimserverd stop/etc/init.d/tier1slp stop/etc/init.d/slpd stop/etc/init.d/slpd start/etc/init.d/tier1slp start/etc/init.d/cimserverd start

v Windowsnet stop wmicimservernet stop tier1slpnet stop ibmsa

Wait five minutes for all processes to be fully stopped, then run thesecommands:net start ibmsanet start tier1slpnet start wmicimserver

Cloned Linux machines are not discoveredThis problem affects Linux machines that were cloned.

Problem

When a Linux machine is cloned one or more times, some of the resultingmachines are not discovered, or else they are merged.

Explanation

The Secure Shell (ssh) fingerprints are identical between the machines, so thediscovery process does not recognize them as individual endpoints.

Resolution1. In IBM Systems Director, delete any discovered resources for both the original

system and the cloned or copied systems, including servers and operatingsystems.

2. For each cloned machine, regenerate the keys for ssh by using the followingcommands:ssh-keygen -q -f /etc/ssh/ssh_host_key -N ’’ -t rsa1ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N ’’ -t rsassh-keygen -f /etc/ssh/ssh_host_dsa_key -N ’’ -t dsa

Do not provide a passphrase.For more information about ssh-keygen, see the documentation for the Linuxdistribution running on the cloned machines.

3. Restart the ssh service for each machine.

128 IBM Systems Director Troubleshooting and Support Guide

4. If the cloned machine has Common Agent Services (CAS) installed, ensure thatthe CAS GUID is unique. For more information, see “Discovering systems thatuse a mirrored image.”

5. Discover the cloned machines.

Common Agent managed systems are not displayedThis problem affects Common Agent.

Problem

Common Agent managed systems are not displayed in the IBM Systems DirectorWeb interface.

Resolution

To correct this problem, make sure that the system is turned on, Common Agent isrunning, and the network connection is reliable.

If you are using Tivoli common agent, ensure that the hostname resolves correctly.For more information, see this topic: Requirements for common agent installation.

Discovery does not create an SNMP managed resource for a IBMBladeCenter network deviceThis problem affects IBM BladeCenter network devices only.

Problem

The IBM BladeCenter chassis discovery process does not create an SNMP managedresource 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 isnot set to “public,” the IBM BladeCenter chassis discovery will not create anSNMP managed resource for that switch module. Also, the community name in theSNMP agent that is installed on the switch module must match the communityname of the SNMP managed resource displayed in the IBM Systems Director Webinterface for the SNMP managed object to stay online.

Resolution

Make sure that the SNMP community name in the SNMP agent of the switchmodule is set to “public” and matches the community name of the SNMPmanaged resource displayed in the IBM Systems Director Web interface.

If you must use an SNMP community name other than “public” with a switchmodule, 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 asOnline.

Troubleshooting and support 129

3. Set the community name in the SNMP agent that is installed on the switchmodule to the new value. The IBM Systems Director Web interface displays thestatus of the switch module as Offline.

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 Agentwas installed only moments beforeThis problem affects discoveries that use the Common Information Model (CIM)protocol to discover Windows Server 2008 R2 systems on which Platform Agentwas installed only moments before.

Problem

When using the CIM protocol to discover resources, the discovery will fail whentrying to discover Windows Server 2008 R2 systems on which Platform Agent wasinstalled only moments before.

Explanation

After installing Platform Agent, Platform Agent services run an initializationprocess. On systems running Windows Server 2008 R2, the Platform Agentinitialization process takes several minutes to complete. If a request to discover thiskind 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 runningWindows Server 2008 R2, wait for approximately 8 minutes before trying todiscover the system. Waiting 8 minutes gives Platform Agent services time tocomplete the initialization process, which enables discovery to successfullydiscover the system.

Discovery finds two operating systems for one discoveredresourceThis problem affects the discovery of a single resource that has multiple IPaddresses where one or more of those IP addresses cannot be resolved correctly bythe DNS server.

Problem

When discovering a single resource that has multiple IP addresses, the results inthe 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 performthe 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.

130 IBM Systems Director Troubleshooting and Support Guide

c. Rediscover the resource.2. Request access to both of the operating systems, which merges them into a

single operating system.

Note: If the name of the merged operating system becomes the unresolvable IPaddress, simply rename it.

Discovery results do not show CIM Remote Service AccessProtocolThis problem affects some discoveries that use the Common Information Model(CIM) protocol.

Problem

After discovering a resource, you can view available Remote Service AccessProtocols (RSAPs) for that resource in the discovery results (properties page or inother 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 CommonAgent Services protocol, if present, handles the transport for CIM communication.This behavior works as designed, because tunneling CIM communication throughCommon Agent Services helps reduce the number of open, active ports that arerequired by IBM Systems Director.

Investigation

Determine that CIM communication is working properly by performing thefollowing 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 isworking properly. Go to step 4.

3. If running the cli command does not correctly return the namespaces, thenCIM is not working properly. Make sure that the Agent installed on theresource is properly configured.

4. From IBM Systems Director Server, run the command that is appropriate foryour operating system and Platform Agent level:v On AIX or Windows:

slp_query --type=* --address=<ip_of_Agent-managed_resource>

v On Linux:/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.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 communicationworks properly even if the RSAP is not shown. If the command results do notshow both wbem entries, a different problem exists.

Explanation

The behavior described in this topic is a known limitation.

Troubleshooting and support 131

IBM Systems Director Server can lock upon RHEL5 and SLES10Common Agent discoveryThis problem affects users who attempt to discover a RHEL5 or SLES10 CommonAgent.

Problem

Attempts to discover Red Hat Enterprise Linux, version 5.0 or SUSE LinuxEnterprise Server 10 Common Agents might cause the IBM Systems Director Serverto lock itself.

Explanation

This problem occurs if the xen-libs and xen-tools packages for RHEL5 or SLES10have not been removed before installing the IBM Systems Director Server.

Resolution

Run the following commands to remove the packages from your system beforeinstalling IBM Systems Director Server:32-bitrpm -e --nodeps xen-libsrpm -e --nodeps xen-tools

64-bitrpm -e --nodeps --allmatches xen-libsrpm -e --nodeps --allmatches xen-tools

Reboot after your run the commands.

Local system is not discovered at startupThis problem affects tasks that require that the local system is discovered at serverstartup.

Problem

The system on which IBM Systems Director Server resides is not discovered whenthe server is started. The following IBM Systems Director tasks are examples ofthose that will fail when the local system is not discovered:v Resource navigation of the local systemv Update IBM Systems Directorv Credentials

Explanation

The system on which IBM Systems Director Server is installed must be discoveredand accessible or certain tasks will fail.

Resolution

The following are some potential reasons why the system was not discovered andpossible resolutions for each:

IBM Systems Director Server has just started and the agent might not be fullystarted yet.

Wait 15 minutes and try again.

132 IBM Systems Director Troubleshooting and Support Guide

A firewall installed on the system on which IBM Systems Director Server isinstalled is preventing communication between the server and agent.

Ensure that the appropriate ports are set to allow access through thefirewall. For information about which ports to set, see “All availableports”.

Non-IBM hardware shown as offline after discoveryThis problem affects non-IBM hardware. After discovery, the Server resource (notthe Operating System resource) that represents the hardware has an access state ofOffline.

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 stateof Offline. The access state might first be labeled Unknown, but after using theVerify 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-bandcommunication. See the system documentation for information about configuringthe BMC.

SSH protocol not discovered for AIX IPv6 agentsThis problem affects systems running AIX.

Problem

The SSH protocol is not discovered for AIX agents running in an IPv6environment.

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 thisproblem.ssh: connect to host <ipv6 address> port 22: Connection refused

Resolution1. Edit /etc/ssh/sshd_config so that the configuration for Port 22 is as follows:

#Port 22AddressFamily anyListenAddress 0.0.0.0ListenAddress ::

2. Stop sshd services stopsrc -s sshd

3. Restart sshd services startsrc -s sshd

Troubleshooting and support 133

System discovery job log does not list newly discoveredsystemsThis problem affects the system discovery job log.

Problem

After the system discovery job completes, one or more newly discovered systemsmight not be listed in the job log.

Explanation

This behavior occurs because the manageable element is created asynchronously.When the manageable element for a newly discovered system is not fully createdwhen the discovery task completes, that system is not listed in the job log. Job logsfor subsequent discoveries (that start after the manageable element is created)show that the system was previously discovered.

Note: The tables that list manageable resources are unaffected by this behavior. Forexample a newly discovered system that is not listed in the job log is visible inResource Explorer.

Resolution

The behavior described in this topic is a known limitation.

System discovery results in assignment of the IP addresses toexisting systemsThis problem affects primarily networks where DHCP is used, but might occurwhenever there is not a consistent mapping from a DNS host name to a physicalsystem.

Problem

When you perform a discovery action to find new systems, the systems are notdisplayed in the resources views. Instead, the IP addresses seem to be assigned toexisting systems.

Explanation

The IBM Systems Director Server uses the host names of the managed systems tomatch systems that are discovered using multiple protocols or at different times.Having a consistent mapping of host names to systems ensures that other systemsare not matched to previously discovered systems.

Example: Consider a system at address 192.168.1.5 in a DHCP environmentwithout dynamic DNS. Suppose the host name that resolves to that address iss5.example.com. Later, the address of the system changes to 192.168.1.9, whichmaps 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 differenthost name, and a new manageable system is created. Likewise, if another systemacquires the host name s5.example.com and is discovered, IBM Systems Directorwill consider it as the same system as originally discovered at s5.example.com.Discovering only Common Agents causes the system matching process to use theunique identifier of the systems, and the host name is not used.

134 IBM Systems Director Troubleshooting and Support Guide

Resolution

IBM Systems Director requires that a host name is consistently resolved to thesame system, even if the IP address of the system changes. Try the followingsolutions 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 SNMPThis problem affects switch and bridge modules only.

Problem

When you attempt to discover a switch or bridge module using SNMP, thediscovery fails.

Explanation

This problem affects switch and bridge modules that do not correctly provide theMAC address for the management connection in SNMP. The MAC address isrequired for IBM Systems Director to uniquely identify the module that has beendiscovered.

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 sowill discover the I/O module.

Note: If the chassis was discovered before the I/O module was inserted, youcan 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 VerifyConnection.

– Select the affected chassis and click Actions > Inventory > View and CollectInventory and perform an inventory collection.

Inventory troubleshootingThis section provides information for specific problems and workaroundsassociated with the Inventory task.

Inventory collection completes with errorsThis problem affects collecting inventory for System x systems that are runningLinux.

Troubleshooting and support 135

Problem

Collecting inventory for a System x system that is running Linux completes witherrors.

Explanation

To retrieve vital product data (VPD) information from the system BIOS of a Systemx system that is running Linux, IBM Systems Director must have root access. If theinventory collection does not have root access, it cannot read the physical memoryto get this information. In this situation, collecting inventory without root accesscauses inventory collection to complete with errors. Requesting access to thesystem as a user that is in the root group does not satisfy this access. IBM SystemsDirector must either run as the root user explicitly or use the sudo utility.

Resolution

When requesting access to and collecting information for a System x system that isrunning 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 toconfigure those systems to allow IBM Systems Director to run as a user otherthan root.

For more information about using the sudo utility to configure agentless-managedsystems to use a user other than root, see “Configuring access to agentlessmanaged systems.”.

Inventory collection fails when Common Agent or Platform Agentis not at the latest levelThis problem affects IBM Systems Director Server.

Problem

Inventory collection fails if IBM Systems Director Server is an older version thanCommon Agent or Platform Agent.

Resolution

IBM Systems Director Server must be the same version or a later version thanCommon Agent or Platform Agent. Update your IBM Systems Director Serverinstallation.

Inventory collection fails to complete for IBM BladeCenterchassisThis problem affects only IBM BladeCenter chassis products.

Problem

You discovered the IBM BladeCenter chassis successfully, but when you runinventory collection on it, the collection does not complete.

136 IBM Systems Director Troubleshooting and Support Guide

Resolution

Before running inventory collection on a BladeCenter chassis, you must enableSNMP by using the Management Module Network Configuration component ofconfiguration manager. See “Configuring an IBM BladeCenter managementmodule” in the IBM Systems Director Systems Management Guide for moreinformation.

Collecting inventory fails to display information for EmulexproductsThis problem affects inventory collection for Emulex products on systems that arerunning all platforms except the IBM customized image ESXi.

Problem

After you collect inventory, the View and Collect Inventory page does not displayinformation for one or more Emulex products. The most likely cause of thisproblem is that the Emulex driver kit either is not installed on the system that iscollecting inventory or is not working correctly. For systems running Linux (64-bit),it is also possible that the 32-bit shared object library “libnl” is not installed.

Explanation

Collecting Emulex product inventory requires both of the following (if applicable):v A properly-functioning Emulex driver kit must be installed.v On Linux (64-bit) systems, the 32-bit shared object library must be installed in

addition to the 64-bit shared object library.

Investigation

First, determine whether the Emulex Adapter is working on the system.

Linux: Run the command lspci | grep -i emulex. If the result does not includethe Emulex Adapter, install the Emulex adapter drivers and update the firmware.

Windows:

1. Go to Start > Settings > Control Panel. Double-click System. Click theHardware tab and select Device Manager.

2. Look for these listings:v Under Network adapters, look for “Emulex Network Interface Card (NIC)”

or “Converged Network Adapter (CNA)”.v Under SCSI and RAID controllers, look for “Emulex Host Bus Adapter

(HBA)”If none of them are listed, install the Emulex adapter driver package that wasincluded with your Emulex product and update the firmware. See the Emulexdownload site for firmware updates (http://www.emulex.com/downloads/emulex.html).

3.

To determine whether the Emulex driver kit is part of the problem, verify that theEmulex driver kit is installed on the system that is collecting inventory and that itis working correctly:

Linux

Troubleshooting and support 137

1. On the system that is collecting inventory, from a command line, run thecommand rpm -qa | grep -i elxocmcore.

2. Look for the Emulex driver kit, which has a file name similar toelxocmcore*.rpm or elxocm*rpm, where * represents a string of alphanumericcharacters. If the kit is not listed, it is not installed.

3. If the kit is installed, on the command line, run the command hbacmd listhbas.4. Look for the manageable Emulex Adapters. If they are not listed, it is likely

that the Emulex driver kit does not work.5. For the systems that are running Linux(64-bit), verify that the 32-bit shared

object library “libnl” is installed. Run the command ls /lib/ | grep -i libnl,if no result is returned, the 32-bit libnl library is not installed.

Windows

1. Open Control Panel > Installed Programs and look for “elxocmcore” or“elxocm”. If the kit is not listed, it is not installed.

2. If the kit is installed, on the command line, run the command hbacmd listhbas.If the results do not include the manageable Emulex Adapters, it is likely thatthe Emulex driver kit does not work.

Resolution

Follow the procedure for the problem you identified.

The Emulex driver kit is not installed or the Emulex driver kit does not work:

Find the kit in the driver package that was included with your Emulexproduct and install it.v Linux: Extract elxocmcore-*.tgz or elxocm-*.tgz, then run the

command ./install.sh to install the driver kit.v Windows: Double-click either elxocmcore-windows-*.exe or

elxocm-windows-*.exe to install the kit.

The 32-bit libnl library is not installedLocate and install this library. It is included on all the 32-bit operatingsystems' distribution media, or you can search online for a differentdownload site.

Inventory collection fails to retrieve firmware informationThis problem affects collecting inventory from IBM Director Agent 6.3 running onAIX 7.1 TL01.

Problem

When collecting inventory in this environment, inventory data is not collectedcompletely. The inventory task completes successfully but certain inventoryinformation, such as firmware inventory, is not available. The problem is in thesysmgt.cimserver.pegasus.rte 2.9.1.30 fileset.

Resolution

Follow the instructions on this Web page and then try running inventory again: Noinventory from Director Agent 6.3 running on AIX 7.1 TL01.

138 IBM Systems Director Troubleshooting and Support Guide

Collecting inventory fails to retrieve software details from bladechassisThis problem affects inventory collection for a blade chassis and firmwareupgrades for the chassis.

Problem

Collecting inventory for a blade center chassis does not return information aboutthe software of the blade chassis, even when the task of collecting inventorycompletes successfully. The missing software information about the blade chassisincludes details about the installed firmware version and any applied updates.Having incomplete software information prevents you from upgrading thefirmware that is installed on the blade chassis.

Resolution

To resolve this problem, modify certain settings for the associated AdvancedManagement Module (AMM). Make the following changes by using themanagement-module Web interface. For more information, see the AMM Webinterface.

After you open and log in to the management-module Web interface, configure thefollowing MM Control network protocol settings:v Enable the SNMPv1 network protocol, and set the trap IP destination to 0.0.0.0

or the SNMP trap receiver IP address.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 inventoryagain for the blade chassis retrieves the missing software information.

Root directory needs more space for AIX and Linux inventorycollectionThis 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 ifthe 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 diskspace to the root directory (/) and delete the directory /tivoli/cce, if it alreadyexists. You must then restart IBM Systems Director. If there is an IBM SystemsDirector Server installed on the system, you must restart it, as well.

Troubleshooting and support 139

Security and requesting access troubleshootingThis section provides information for specific problems and workaroundsassociated with security and accessing resources in the IBM Systems Directorenvironment.

Handling Request Access failuresThere are several actions you can take to investigate and resolve Request Accessfailures on IBM Systems Director Common Agent.

Make sure that the system is not being managed by more thanone agent manager

A Common Agent-managed system can be managed by only one agent manager ata time. Removing the Common Agent-managed operating system resources willnot unregister the Common Agent from the associated agent managers. If thatagent manager is not the agent manager that the IBM Systems Director uses, youmust unregister the Common Agent in order to manage it with IBM SystemsDirector.

Before you unregister the current agent manager, you can query the usma servicedetail information to determine the current agent manager. Issue the followingcommand that is applicable for the managed system operating system:AIX or Windows

slp_query --type=* --address=localhostLinux

/opt/ibm/icc/bin/slptool -u 127.0.0.1 findattrs service:management-software.IBM:usma

On the Common Agent-managed system, issue the following commands that isapplicable for the managed system operating system:AIX or Linux

install_root/agent/runtime/agent/toolkit/bin/configure.sh -unmanaged -forceWindows

<install_root>\agent\runtime\agent\toolkit\bin\configure.bat -unmanaged -force

Where install_root is the root directory of your IBM Systems Director CommonAgent installation.

Ensure you are using the correct userid or passwordv Check by manually logging into the resource via ssh, telnet (tn) or mstsc.exe to

confirm that the password is correct.v Many browsers will pre-fill the password field. Empty it and make sure it is the

right password.

Check the firewall

Request Access requires a reliable connection between the IBM Systems DirectorServer and Common Agent. You will need a connection in both directions: agent toserver and server to agent. Make sure you can ssh, telnet (tn) or mstsc.exe fromeither direction. Example checks are below:Agent side

telnet AM_IP 9513, make sure the connection works

140 IBM Systems Director Troubleshooting and Support Guide

AIX or Linux

install_root/agent/runtime/agent/toolkit/bin/checkconn.sh -host AM_IP -password AM_password

Windows

<install_root>\agent\runtime\agent\toolkit\bin\checkconn.bat -host AM_IP -password AM_password

For example, the checkconn command might display the following information:BTC8614I The connection to the agent manager has been established successfully.

Server side

telnet Agent_IP 9510, make sure the connection works

Note: AM_IP is the IP address of the agent manager. AM_password is the registerpassword for the agent manager.

Check the time difference

As a general rule, the time difference between Common Agent and IBM SystemsDirector Server - adjusted for time zone - should not be more than 1 hour. Pleaseensure that the system clocks on the systems that contain IBM Systems DirectorServer and Common Agent remain synchronized.

Check to see if the IBM Systems Director Server IP address haschanged

If there is an IBM Systems Director Server IP address change, please restart theserver before issuing a Request Access. A correct server IP address is a prerequisitefor Request Access.

You can run the following commands to check the IP address.

Note: AM_IP is the IP address of the agent manager. AM_password is the registerpassword for the agent manager.wget -O AgentMgr.Info http://AM_IP:9513/AgentMgr/Info

AIX or Linux

install_root/lwi/runtime/agentmanager/toolkit/bin/HealthCheck.sh -toolkitPassword AM_password

Windows

<install_root>\lwi\runtime\agentmanager\toolkit\bin\HealthCheck.bat -toolkitPassword AM_password

For example, the HealthCheck command might display the following information:CTGEM2470I It is the agent manager instance ID: 375ec6e115283ddaab37ec3b80771062

AGENT_CONFIG_SERVICE = https://127.0.0.1:9512/AgentMgr/AgentConfigurationCRL_REQUEST = http://127.0.0.1:9513/AgentMgr/CRLRequestMULTI_SCHEDULER_SYNCHRO_SERVICE = https://127.0.0.1:9512/AgentMgr/MultiScheduleSynchronizerFILE_DOWNLOAD_SERVICE = http://127.0.0.1:9513/AgentMgr/PatchesUPGRADE_SERVICE = https://127.0.0.1:9512/AgentMgr/UpgradeServiceREGISTRATION_SERVICE = https://127.0.0.1:9511/AgentMgr/RegistrationSERVICE_CATALOGUE_REQUEST = http://127.0.0.1:9513/AgentMgr/ServiceCatalogueRequestAGENT_MANAGER_QUERY = http://127.0.0.1:9513/AgentMgr/AgentManagerQueryAGENT_QUERY = https://127.0.0.1:9512/AgentMgr/AgentQueryMIGRATION_SERVICE = https://127.0.0.1:9512/AgentMgr/MigrationServiceMANAGER_CREDENTIALS_SERVICE = https://127.0.0.1:9512/AgentMgr/AuthAdminTRUSTSTORE_REQUEST = http://127.0.0.1:9513/AgentMgr/TrustedCertificateQueryPATCH_SERVICE = https://127.0.0.1:9512/AgentMgr/PatchServiceCOMMON_AGENT_QUERY = https://127.0.0.1:9512/AgentMgr/CommonAgentQueryCERT_REVOCATION_SERVICE = https://127.0.0.1:9512/AgentMgr/CertificateRevocationSCHEDULER_ADMIN_SERVICE = https://127.0.0.1:9512/AgentMgr/ScheduleManagerDELETE_AGENTS_SERVICE = https://127.0.0.1:9512/AgentMgr/DeleteAgentsSCHEDULER_SYNCHRO_SERVICE = https://127.0.0.1:9512/AgentMgr/ScheduleSynchronizerVERSION_SERVICE = http://127.0.0.1:9513/AgentMgr/VersionDEREGISTER_SERVICE = https://127.0.0.1:9512/AgentMgr/DeregistrationServiceCONFIG_UPDATE_SERVICE = https://127.0.0.1:9512/AgentMgr/ConfigurationUpdateCERT_RENEWAL_SERVICE = https://127.0.0.1:9512/AgentMgr/CertificateRenewalFILE_ADMIN_SERVICE = https://127.0.0.1:9512/AgentMgr/PatchAdminINFO_PAGE = http://127.0.0.1:9513/AgentMgr/InfoIPADDRESS_SERVICE = http://127.0.0.1:9513/AgentMgr/IPAddressJOB_MANAGER_SERVICE = https://127.0.0.1:9512/AgentMgr/JobManager

CTGEM2450I The Health Check tool passed.

Note: AM_IP is the IP address of the agent manager. AM_password is the registerpassword for the agent manager.

Check the Common Agent status

Request Access requires that the Common Agent is in good status. You can run thefollowing queries to check agent status:

Troubleshooting and support 141

AIX or Linux

install_root/agent/runtime/agent/bin/endpoint.sh statusRunning.install_root/agent/runtime/agent/bin/agentcli.sh connector aliveBTC7101I The connector is active.

Windows

<install_root>\agent\runtime\agent\bin\endpoint.bat statusRunning.<install_root>\agent\runtime\agent\bin\agentcli.bat connector aliveBTC7101I The connector is active.

If the Common Agent status is not active, complete the following steps:

1. Issue the following command to check to make sure that the SLP is in anoperational state:rcc-pok-idg-1992:~ # ps -ef|grep slproot 15198 15059 0 03:18 pts/0 00:00:00 grep slpdaemon 21276 1 0 Apr23 ? 00:01:13 /opt/ibm/icc/bin/slpdroot 23450 1 0 Apr23 ? 00:00:00 /opt/ibm/platform/bin/tier1slp

2. Make sure that the DNS is set correctly set on the agent system. If no DNS isconfigured, check the hosts files on the agent system. The following entry isavailable:- 127.0.0.1 localhost- ::1 localhost

Note: - ::1 localhost only applies if there are IPv6 addresses.Every IP address should be mapped to the hostname of the endpoint.

Check common agent services (CAS) status

Request Access requires that the CAS client is in good status. Below is an examplequery for checking CAS status:USERID@myfsm1:~> smcli getAgentManagers

*******************************************Agent manager id/name : 45C7862A505D34FC9F8D8C8D6D3850E5Agent manager versoin : 1.4Agent manager ip : 10.10.6.60Is this default? : trueAgent Manager userid : rootAgent Manager port : 9511Agent Manager ipaddress list: 10.10.6.60, fd55:faaf:e1ab:1b09:214:5eff:fe5a:3035, fe80:0:0:0:214:5eff:fe5a:3035,Is this Embedded: true*******************************************

USERID@myfsm1:~> smcli queryAgentsAgent--------------- AGENT [0dac826ed7d73d2883034c99a2286f72] ---------------Agent directory = file:///opt/ibm/director/agent/runtime/agent;...Agent registration time: Wed Mar 14 03:33:54 EDT 2012AgentOperationalStatus[0]:AgentContactInfo[0]:

Configure the Common Agent for managed mode

Below are the commands you can use to configure the Common Agent formanaged mode without Request Access. You can then run discovery, which willauto unlock OS or IBM Systems Director Server resources.AIX or Linux

install_root/agent/runtime/agent/toolkit/bin/configure.sh -amhost AM_IP -passwd AM_password -force

Windows

<install_root>\agent\runtime\agent\toolkit\bin\configure.bat -amhost AM_IP -passwd AM_password -force

142 IBM Systems Director Troubleshooting and Support Guide

Note: AM_IP is the IP address of the agent manager. AM_password is the registerpassword for the agent manager.

Access request to IBM Director Agent 5.20 failsThis problem affects IBM Director Agent 5.20 on systems running AIX.

Problem

When IBM Systems Director Server 6.1 requests access to an AIX system runningIBM Director Agent 5.20, the request access fails immediately even though the username and password are correct.

Explanation

The user name used for the request access is not authorized. In theNativeUserGroupsAIX.prop file, the line priv.groups.SecMgr defines the groupsthat 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 theNativeUserGroupsAIX.prop file and view the predefined IBM SystemsDirector security groups.

2. In the /etc directory, edit the group file to add the user name to one ofthe predefined groups and save the changes. For example, to add theroot 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 DirectorAgent-managed system

1. In the /etc directory, view the group file to determine the group towhich your user name belongs. For example, the following lineindicates that the root user belongs to system group:system:!:0:root,esaadmin

2. In the /opt/ibm/director/data directory, edit theNativeUserGroupsAIX.prop file.

3. Add the affected group to the priv.groups.SecMgr line. For example, toadd 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 themanaged system:install_root/bin/twgstop

where install_root is the root directory of the IBM Director Agentinstallation.

5. Start IBM Director Agent by typing the following command on themanaged system:install_root/bin/twgstart

Troubleshooting and support 143

where install_root is the root directory of the IBM Director Agentinstallation.

SNMP remote service access point of a switch goes offlineafter switch creation and stays offline after request access

This problem affects users who are trying to create a switch through request accessto a BladeCenter.

Problem

This problem occurs when a switch is created after requesting access to aBladeCenter. The IBM Systems Director Web interface shows the SNMP serviceaccess status of the switch as Offline and no access; the switch access status mightbe partially unlocked or locked. If you request access to the switch by using therequest access task and typing a user ID and password, the access status might stillshow that the SNMP remote service access point of the switch is offline with noaccess.

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 > ConfigureAccess.

Explanation

When the switch is created, IBM Systems Director tries to use the defaultcommunity name public or the community names in <directorinstall>\data\snmp\snmpdevice\snmpCommunities.properties and the SNMPv1protocol to verify the SNMP connection. If the community name is not the defaultor is not listed in the properties file, the verify connection task fails, which causesthe 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 canprovide 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 beunlocked 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 restrictionThis problem affects IBM Systems Director Server.

144 IBM Systems Director Troubleshooting and Support Guide

Problem

When requesting access to a secured system from the Request Access page, youcannot enter a password longer than 45 characters.

Explanation

The Request Access task has a password length limit of 45 characters. Additionalcharacters will be ignored. You cannot gain access to a managed system using auser credential that has a password greater than 45 characters in length.

Resolution

To correct this problem, shorten the password on the managed system to gainaccess.

Access request to a managed system running SUSE LinuxEnterprise Server fails

This problem affects access requests to managed systems that are installed withCommon Agent or Platform Agent and are running SUSE Linux Enterprise Server.

Problem

When you request access to a Common Agent managed system or Platform Agentmanaged system that is running SUSE Linux Enterprise Server, the access requestfails and the affected system is not displayed as type Server in the IBM SystemsDirector Web interface. That is, the agent is discovered, but access to the system isnot obtained.

Investigation

Check the /etc/host file on the affected system to determine if an entry for the IPaddress 127.0.0.2 exists. In the file, determine if a line similar to the following lineis present:127.0.0.2 server.company.com server

wherev 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 IPaddress 127.0.0.2. This entry results in IBM Systems Director identifying the IPaddress of the affected system as 127.0.0.2. Some IBM Systems Director functionson the affected managed system and the management server will fail to work asdesigned when this situation occurs.

Important: Using the DNS and host name configuration function of the YASTsystem tool inserts a 127.0.0.2 entry into the /etc/hosts file.

Resolution

To resolve this problem, complete the following steps:

Troubleshooting and support 145

1. In the /etc/hosts file on the affected managed system, comment out the127.0.0.2 entry. Insert the pound sign symbol (#) in the first character positionof the entry, for example:# 127.0.0.2 server.company.com server

wherev server.company.com is the fully qualified host name.v server is the short host name.

2. Save the /etc/hosts file.3. Restart the affected managed system.4. In the IBM Systems Director IBM Systems Director Web interface, delete the

affected system.5. Run System Discovery to discovery the affected system.

Agentless or Platform-Agent managed resource cannot beaccessed

This problem only affects Agentless or Platform-Agent managed resources runningIBM i.

Problem

An Agentless or Platform-Agent managed resource that is running IBM i cannot beaccessed.

Resolution

To resolve this problem, make sure that Open SSH, *BASE and Option 1, LicensedProduct Offering 5733-SC1 is installed and configured. Also make sure that SSH isrunning on the affected Agentless or Platform-Agent managed resource.

IsLocked property always shows false for case-sensitiveLDAP user names

This problem affects IBM Systems Director Servers running on systems withLightweight Directory Access Protocol (LDAP).

Problem

After locking LDAP users, the IsLocked property for the users still displays as falsein the console and command line interface.

Explanation

LDAP users whose names are case-sensitive can display a value of false in theIsLocked property, even though the user is locked. You can check the value ofIsLocked property using the smcli lsuser -l command or through the webconsole.

Resolution

To correct this problem, complete the following procedure:1. Navigate to the lwi\security\jaas\addtlconfig directory and create a new

Java Authentication and Authorization Service (JAAS) configuration file namedfilename.config, where filename can be a string of your choice.

146 IBM Systems Director Troubleshooting and Support Guide

2. Add the following entry in to the configuration file:Jaas2.LdapNoCase{com.ibm.security.jaas2lwi.Jaas2ComplexLoginModule required debug=falseindex1=Jaas2.Ldap failedLoginHandler=com.ibm.security.jaas2lwi.FailedLoginHandler failedListener1=Jaas2.LockFailedUser;};

3. Open the lwi\conf\security.properties file and comment out the followingline:#com.ibm.lwi.security.jaas.failedLoginHandler.normalizeUsernameClass= com.ibm.security.jaas2lwi.NativeNormalizeUsername

4. Open the lwi\conf\overrides\securityLDAP.properties file and make thefollowing changes:a. Comment out the following line:

#com.ibm.lwi.security.jaas.failedLoginHandler.normalizeUsernameClass= com.ibm.security.jaas2lwi.NativeNormalizeUsername

b. Change the JAAS index to the following:com.ibm.lwi.security.jaas.jaasindex=Jaas2.LdapNoCase

5. Save your changes to the configuration files.6. Restart the server.

Managed resource state is UnknownThis problem affects IBM Systems Director Server.

Problem

After you change encryption settings, certain managed resources cannot bemanaged 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 completedimmediately. During the delay, IBM Systems Director Server cannot manage thesystem.

v If you disable encryption on the management server, encrypted managedsystems can no longer be managed. However, these systems might seem to bemanageable for a certain period before they are displayed as locked.

Resolution

To correct this problem, force an immediate exchange of keys on a particularmanaged resource by requesting a presence check.

Credential mapping wizard does not finish when editing acredential mapping

This problem affects credential configuration.

Troubleshooting and support 147

Problem

When editing a credential mapping, clicking Finish on the summary page of thecredential mapping wizard does nothing and no message is displayed to indicatethat there is a problem.

Explanation

The credential mapping wizard cannot complete successfully if one or more of thefollowing situations occurs after you have launched the wizard to edit a credentialmapping:v The credential is deletedv The credential mapping is deleted

Resolution

Close the credential mapping wizard.

Settings permission is not available to users in groups otherthan smadmin

This problem affects the Microsoft Internet Explorer and Mozilla Firefox browsers.

Problem

When you assign a role with only the Settings permission to a user that is in agroup other than smadmin, the user does not receive authorization to modifysettings as expected. When that user signs in to the IBM Systems Director Webinterface, the Settings option is not displayed.

Resolution

To have the authorization to see the Settings option in the IBM Systems DirectorWeb interface and modify the settings, the user must belong to the smadmingroup.

Hardware Management Console access state becomesunknown after supplying incorrect credentials

This problem affects Hardware Management Consoles.

Problem

When you request access to a Hardware Management Console using incorrectcredentials, the access request fails and the Hardware Management Console'saccess state changes to Unknown. Also, you are not able to request access againand verification of the connection will fail.

Explanation

Incorrect credentials prevent access to a Hardware Management Console. Youcannot access request again because the Hardware Management Console is not in astate of No Access.

148 IBM Systems Director Troubleshooting and Support Guide

Resolution

Remove the Hardware Management Console and then rediscover the sameHardware Management Console.

Trust domain users cannot log onThis problem affects trust domain users that cannot log on to the IBM SystemsDirector Web interface on Windows.

Problem

In a trust domain environment with domain A and domain B, IBM SystemsDirector Server is installed on system C, which belongs to domain A. Users ofdomain A and domain B belong to the IBM Systems Director Server smadmingroup on system C. Only the domain user (the domain A user) has the correctauthority to log on to the IBM Systems Director Web interface while the trustdomain user (the domain B user) has no authority to log on to the IBM SystemsDirector 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 Webinterface: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. On the Log On page, select This account: and click Browse.5. Select the new user (user D) from domain A and click OK.6. Enter and reenter the correct password for user D and click OK.7. Right-click the IBM Systems Director Server service and select Restart.

Spaces are not allowed for LDAP user full DNThis problem affects users who employ LDAP user to login to the IBM SystemsDirector Web interface.

Problem

If you add an LDAP user to the LDAP group and it has spaces at the end of thefull DN, the user will login as unknown.

Resolution

Remove spaces at the end of the LDAP user and re-login. The user will then havecorrect authority in the IBM Systems Director Web interface.

LDAP users unable to login when users in same path exceed500

This problem affects IBM Systems Director Servers running on all systems whenconfigured to use tivoli Directory server as authentication registry.

Troubleshooting and support 149

Problem

IBM Systems Director Servers are unable to allow users to log on to an LDAPserver if the number of users under one path is more than 500.

Explanation

You can check the value of ibm-slapdSizeLimit by editing theids_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, increasethe ibm-slapdSizeLimit parameter to a higher value.

DN values for securityldap.properties must match the LDAPserver 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 tolog 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 havethe correct specification. For example, if the LDAP server base uses uppercase forits DN values, such as dc=DOMAIN,dc=COM, but the values specified in thesecurityLDAP.properties file are in lowercase, such as dc=domain,dc=com, this willcause an error.

Resolution

For IBM Systems Director Servers running on AIX systems, set thecom.ibm.lwi.security.username.caseSensitive flag to false and make sure that thebase DN values specified in the securityLDAP.properties file match the LDAPserver base values.

IBM BladeCenter and System x management troubleshootingThis section provides information about problems and workarounds for the IBMBladeCenter and System x management plug-in. This information includes the IBMBladeCenter and System x specific templates provided for the configurationmanager plug-in.

Access is not granted automatically to switchesThis problem affected switches that use a default user ID and password.

150 IBM Systems Director Troubleshooting and Support Guide

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 theIBM Systems Director Web interface.

IBM Systems Director cannot communicate with out-of-bandsystems

This problem affects systems that IBM Systems Director manages throughout-of-band communication. An affected system must include a managementmodule, advanced management module, Remote Supervisor Adapter, or RemoteSupervisor Adapter II.

Problem

IBM Systems Director fails to communicate with a system that is managed throughout-of-band communication. Examples of failed communication can include:v Access requests failv Inventory collection failsv Configuration manager fails to deploy plans or templates

Investigation

This problem can affect systems that use one of the following components:v Management modulev Advanced management modulev Remote Supervisor Adapterv 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 tocommunicate with these service processors and management modules. Other IBMprograms use the standard TCP Command Mode protocol to communicate withservice processors and management modules also, for example:v IBM Management Process Command-Line Interface (MPCLI)v UpdateXpressv Cluster Systems Managementv Active Energy Manager (Standalone edition)

By default, service processors and management modules are enabled to use thestandard TCP Command Mode protocol and permit only one connection at a timewhen using the standard TCP Command Mode protocol. In this situation, if asystem is communicating with another IBM program that uses the standard TCPCommand Mode protocol, IBM Systems Director Server cannot communicate withthat system. However, you can use the management module or Remote SupervisorAdapter (RSA) interface to increase the number of connections allowed.

Troubleshooting and support 151

Resolution

Close the program that is using the standard TCP Command Mode protocol tocommunicate 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 thenumber of connections permitted when using the standard TCP Command Modeprotocol. Log into the advanced management module Web interface and view theNetwork Protocols page. On this page, the TCP Command Mode section providesa setting that you can change to increase the number of connections. This setting isavailable only for advanced management modules. The default setting for thenumber of connections permitted can vary depending on the firmware versioninstalled. Check the TCP Command Mode section to determine the current defaultsetting.

CIM protocol not discovered on systems running ESXioperating system

This problem affects the managed operating system for a System x system or ablade server that also has VMware ESXi 4.1 installed.

Problem

When IBM Systems Director discovers a managed operating system for a System xsystem or a blade server that also has VMware ESXi 4.1 installed, sometimes theCommon Information Model (CIM) protocol is not discovered.

Explanation

The Service Location Protocol (SLP) daemon running on the ESXi 4.1 operatingsystem might not be working correctly, which causes the previously describeddiscovery problem.

Resolution

Complete the following steps to resolve the problem:1. Telnet to the managed ESXi operating system.2. In the telnet session, restart the SLP service by running the following

command: /etc/init.d/slpd restart. After the command completes, you canend the telnet session.

3. Use the IBM Systems Director Web interface to remove the correspondingmanaged ESXi operating system.

4. Rediscover the ESXi operating system that you just removed.

Configuration manager template troubleshootingThis section provides information about problems and workarounds for theconfiguration manager templates provided by the IBM BladeCenter and System xmanagement plug-in.

Advanced Management Module restarts after applying a plug-inThis problem affects BladeCenter systems that contain an Advanced ManagementModule.

152 IBM Systems Director Troubleshooting and Support Guide

Problem

When you attempt to connect to an Advanced Management Module immediatelyafter applying one of the following templates, you might be unable to get aconnection:v Management Module Network IP Configuration plug-inv Management Module Network SNMP Configuration plug-inv Management Module Ports Configuration plug-in

Explanation

These plug-ins restart the Advanced Management Module after applying atemplate. Typically, it takes several minutes.

Resolution

To avoid this problem, wait several minutes before connecting to the AdvancedManagement Module after applying templates of these plug-ins.

Applying or retrieving the SNMP Agent Configuration failsThis problem affects the SNMP Agent Configuration plug-in.

Problem

When you apply or retrieve the SNMP Agent Configuration to or from a targetdevice, 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 orretrieve the SNMP Agent Configuration to or from target device.

Applying the Management Network Configuration failsThis problem affects the Management Network Configuration template

Problem

You create a Management Network Configuration in which you configure anexternal network. Then, you apply the template to a management module. Whenyou retrieve the current configuration from this management module, you find thatthe external network that you configured in the template is not retrieved.

Explanation

To configure an external network, the blade server must support externalnetworking. If it does not support external networking, the configuration will fail.

Note: Only the JS22 blade servers support external networking.

Creating a VLAN configuration failsThis problem affects Switch Module VLAN Configuration templates.

Problem

When creating a VLAN configuration, the creation fails and you receive thefollowing error message:

Troubleshooting and support 153

A VLAN configuration interface ID is incorrect.

Explanation

The Interface number field is labeled as optional. However, the interface numberis required for some, but not all, switches. Also, different switches have differentsupported 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. Donot leave the field blank.

Switch Interface number

Cisco 0

D-Link 0

Intel 0

Nortel 1 through 127

Deployment of the IP Pool Configuration template fails on anytargeted deviceThis problem affects the Configuration Manager template called IP PoolConfiguration.

Problem

When you deploy a IP Pool Configuration template to any targeted device, thedeployment fails.

Explanation

The IP Pool Configuration template provides a pool of IP addresses to othertemplates, for example Service Processor Network IP Configuration template, thatrequire IP address, gateway, and subnet masks configuration. The affectedtemplates can obtain the IP address, gateway and subnet mask from the IP PoolConfiguration templates.

Therefore, the IP Pool Configuration template cannot be deployed to any targeteddevice. Instead, the IP Pool Configuration template assists other templates thatneed to configure the IP address, gateway, and subnet mask in order to bedeployed to their devices.

Resolution

Do not attempt to deploy the IP Pool Configuration template.

154 IBM Systems Director Troubleshooting and Support Guide

Deployment of the User Authentication Configuration templatefails on any targeted deviceThis problem affects the Configuration Manager template called UserAuthentication Configuration.

Problem

When you deploy a User Authentication Configuration template to any targetedBladeCenter chassis or component, the deployment fails.

Explanation

The User Authentication Configuration template provides the user accountinformation to other templates that require the user name and passwordconfiguration.

Therefore, the User Authentication Configuration template cannot be deployed toany targeted device. Instead, the User Authentication Configuration templateassists other templates that need to configure the user name and password in orderto 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 emptyThis problem affects any configuration manager template that includes IP addressconfiguration.

Problem

When you open the Create Network IP Configuration window by clicking theCreate, Create Like, or Edit buttons, the Get an IP address from the IP addresspool list is empty.

Explanation

At least one IP Pool Configuration must be created before the Get an IP addressfrom the IP address pool list can be populated.

Resolution

Create an IP Pool Configuration. For information, see “Configuring the IP addresspool for IBM Systems Director and System x servers.”

Use the specified IP address selection is unavailableThis problem affects the Switch Protocol Configuration template.

Problem

When you create or edit a Switch Protocol Configuration template, the Use thespecified IP address selection is not available on the Network page.

Troubleshooting and support 155

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 beapplied to multiple switch modules in this chassis and, therefore, multiple IPaddresses are required. The Use the specified IP address selection is not validfor multiple IP address selection.

3. Specify a slot number to indicate that the configuration will be applied to oneswitch. Subsequently, the Use the specified IP address selection is enabled onthe Login Configuration page.

Full access to a QLogic or Nortel switch is not permitted withuser 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 thanthe original equipment manufacturer (OEM) user IDs, only partial access isgranted.

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 moduleplug-ins.”

3. Use the applicable OEM user ID to request access:v QLogic: USERID

v Nortel: admin

The Hardware Log task is not availableThis problem affects System x systems.

Problem

When you right-click a System x system, the pop-up menu does not provideHardware Log as a selection. Also, if you select a System x system and clickActions, the Hardware Log task is not available as a selection.

Investigation

In the table, view the affected resource row:

156 IBM Systems Director Troubleshooting and Support Guide

v In the Type column, determine if the resource is of type Operating System orServer.

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. Thisresource type represents the service processor. You must have full access to theresource.

You also can work with Common Agent or Platform Agent. For Common Agentand Platform Agent, in order to use the Hardware Log task the following criteriamust be met: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 IIv Remote Supervisor Adapterv IBM BladeCenter management modulev 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 thatresource to access the hardware logs. If there is no related resource of typeServer, discover and request access to the service processor of the affectedsystem.

After you have full access to the Server resource, the Hardware Log task isavailable on the pop-up menu for both the Server and Operating Systemsresources.

Incorrect events reported for NICs that have a teamingconfiguration 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 asactive-standby. The problem is limited to NICs installed in managed systems thatare running any supported Windows operating system.

Problem

When a network interface card (NIC) in a managed system has a teamingconfiguration of active-standby, IBM Systems Director incorrectly reports someevents for that NIC.

Troubleshooting and support 157

Note: Usually, an NIC is configured as active-standby only when the managedresource contains more than one active NIC.

Explanation

Currently NIC teaming supports only an active-active configuration. Because NICteaming does not support an active-standby configuration, associated events arelimited to SwitchOver and SwitchBack. Look for NIC teaming events in theSystems Director Event Log for the managed server (out-of-band) and in theService Processor Console web user interface.

Table 4. Expected and reported events for NIC with teaming set to active-standby

NIC teaming Symptom Expected event1Reportedevent2

Primary = FailedSecondary = Active

Primary NIC fails; teamingswitches from primaryNIC to secondary NIC

SwitchOver SwitchOver

Primary = ActiveSecondary = Standby

Primary NIC comesonline, teaming switchesfrom secondary NIC toprimary NIC

SwitchBack SwitchBack

Primary = ActiveSecondary = Failed

Standby NIC fails Offline SwitchOver

Primary = ActiveSecondary = Standby

Standby NIC comes online Online SwitchBack

1: A network interface card with a teaming configuration of active-active correctly reportsthe expected NIC events.

2: In a Broadcom “Active-Standby” NIC teaming environment with “Auto-Fallback” modedisabled, Systems Director will not report these events. Instead, either Offline or Onlineevents will be reported according to the Primary or Secondary NIC status.

Resolution

The problem identified in this topic is a known limitation for NICs with a teamingconfiguration of active-standby.

LED Status column is unavailable in Resource ExplorerThis problem affects resources that do not support light path diagnostics.

Problem

When viewing a group of resources in Resource Explorer, you attempt tocustomize 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 ResourceExplorer view support light path diagnostics. In IBM Systems Director 6.1, theOperating System and Computer System resource types support light pathdiagnostics. Also, the default groups called All Operating Systems and All Systemscan display the LED Status column.

158 IBM Systems Director Troubleshooting and Support Guide

Resolution

View a group that includes only the resource types that support light pathdiagnostics. Then, click Actions > Columns and add LED Status to the Selectedcolumns list.

LED Status column does not report hardware problemsThis problem affects systems that support light path diagnostics: System x systemsand IBM BladeCenter chassis.

Problem

A system has one or more light path diagnostic LEDs turned on. However, whenyou view the system in Resource Explorer, the LED Status column always reportsthe status as OK. Also, no light path diagnostic LED events are generated.

Explanation

Currently, IBM Systems Director provides LED Status support for System xsystems and IBM BladeCenter chassis. System x systems must have CommonAgent or Platform Agent installed. Otherwise, the LED Status will not function andthe reported status will default to OK.

It is also possible that the affected system requires an updated Intelligent PlatformManagement Interface (IPMI) driver installed on it.

Resolution

Install Common Agent or Platform Agent on the affected System x system. If thelight path diagnostics LED Status column still reports OK, update the IPMI driveron the system.

Out-of-band events are not configured correctlyThis problem affects events that are sent to IBM Systems Director throughout-of-band communication.

Problem

The Service Processor > Configuration event with a condition value of Failed islogged in the IBM Systems Director event log. This event is generated by IBMSystems Director Server when it determines that out-of-band events are notconfigured correctly.

Investigation

This problem can affect systems that use one of the following service processors ormanagement modules:v Management modulev Advanced management modulev Remote Supervisor Adapterv Remote Supervisor Adapter IIv Intelligent Platform Management Interface (IPMI) baseboard management

controller (BMC)

Troubleshooting and support 159

Explanation

When you gain access to the system, the affected service processor or managementmodule is configured automatically to send out-of-band events to IBM SystemsDirector Server. However, if a service processor or management module hasexceeded its maximum number of alert recipients, the automatic configuration willfail and the Service Processor > Configuration event with a condition value ofFailed is generated.

Table 5. Maximum number of alert recipients

Service processor or management module Maximum number of alert recipients

Management moduleAdvanced management moduleRemote Supervisor AdapterRemote Supervisor Adapter II

12

IPMI BMC Typically 4, but might vary by system

Resolution

To resolve this problem, reduce the number of alert recipients for the affectedservice processor or management module and then add IBM Systems DirectorServer as an alert recipient. You can check the number of alert recipients using theconfiguration manager task called Current® Configuration. To reduce the numberof alert recipients, configure the alert-recipient settings using the applicableconfiguration manager template: Service Processor Alert Recipients or ManagementModule Alert Recipients.

The Service Processor > Configuration event does not have a complementaryresolution event. Therefore, you must manually clear the event from status afteryou have resolved the problem.

Note: IBM Systems Director will not attempt to automatically configureout-of-band events again, unless access to the affected system access revoked andthen access is granted access.

Out-of-band tasks fail on IPMI managed systemsThis problem affects only System x and xSeries® servers with IPMI baseboardmanagement controllers.

Problem

IBM Systems Director tasks that interact out-of-band with servers that haveIntelligent Platform Management Interface (IPMI) baseboard managementcontrollers (BMC) might fail intermittently. Such tasks include Power Management,System Identification, Configuration Manager, and Management ProcessorCommand-Line Interface (MPCLI).

Investigation

Out-of-band IPMI commands use the Remote Mail Checking Protocol (RMCP). Insome network environments, the response packets might be delayed, causingintermittent failure of these commands. Increasing the IPMI-timeout setting canimprove the receipt of the response packets.

160 IBM Systems Director Troubleshooting and Support Guide

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 yourIBM Systems Director installation. Note that this path uses the backslash (\) todelimit the directory; depending on the system that you are using, you mightbe required to enter the path using the forward slash (/).

2. Increase the ipmi.timeout value. The default is 5000, which is equal to 5seconds.

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 install_root/smstop

For Windows net stop DirServer

where install_root is the root directory of your IBM Systems Directorinstallation.

5. Start IBM Systems Director Server by going to the command line, typing theapplicable command, and pressing Enter.

For Linux install_root/smstart

For Windows net start DirServer

where install_root is the root directory of your IBM Systems Directorinstallation.

Power tasks vary by the resourceThis 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 resourcev Whether out-of-band communication is configured for the resource

Note: To access power state management tasks for blade servers in an IBMBladeCenter, you must first discover and request access to the managementmodule.

Predictive Failure Analysis events not reported for Systemx3755 M3 servers

The problem affects the reporting of Predictive Failure Analysis events frommanaged IBM System x3755 M3 servers.

Troubleshooting and support 161

Problem

Platform Agent fails to report Predictive Failure Analysis events for processors orDIMMs that occur on x3755 M3 servers. Because the specified events are notreported, you cannot see any of those events in the event log for the operatingsystem 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 DIMMsv IBM IPMI firmware commands do not work on x3755 M3 servers

Platform Agent cannot report the specified events unless detection of and supportfor Predictive Failure Analysis sensors and support for Predictive Failure Analysissensor events is added to the non-IBM BMCs.

Resolution

The failure to report Predictive Failure Analysis events is a known limitation that isspecific only to System x3755 M3 servers. You can view Predictive Failure Analysisevents in the IBM Systems Director event log for the managed x3755 server(out-of-band). Additionally, you can use the service processor console web interfaceto view the events.

Previously discovered blade server does not show associatedIP address

This problem affects a previously discovered blade server.

Problem

After discovering a BladeCenter chassis, the managed system is visible but not anassociated IP address.

Explanation

Discovering a BladeCenter chassis does not automatically discover the associatedIP address. IBM Systems Director obtains the IP address for a BladeCenter chassiswhen the associated operating system is discovered in band. So, to make the IPaddress visible, you must successfully discover and request access to the associatedoperating system.

Resolution

After discovering a BladeCenter chassis, discover and request access to theoperating system for each managed blade server associated with the BladeCenterchassis.

Switch access state remains Partial Access after accessrequest

This problem affects IBM BladeCenter switches.

162 IBM Systems Director Troubleshooting and Support Guide

Problem

After a switch managed resource is created, the access state of the switch istypically Partial Access. Request access to switch with the correct user ID andpassword, the access states of some switches are still partial access. But firmwareupdate can be successful after request access.

Investigation

Check the access state of the Telnet and HTTP access point using either of thefollowing 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 SNMPv Switch Telnetv Switch HTTPv IBM BladeCenter TCMv 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 managedresource state is OK. If none of the access points are in the Full Access state, theswitch access state is No Access. Otherwise, the switch access state is PartialAccess.

When the switch managed resource is created, IBM Systems Director Serverattempts to unlock the SNMP access point using the public, or user predefined,community name. The chassis access point is unlocked if the switch is createdthrough the chassis. Therefore, the switch is initially in the Partial Access state.

The update manager and configuration manager plug-in use only the Telnet andHTTP access types. When the switch managed resource is created, these two accesspoints are in the No Access state. After you request access using the user ID andpassword, IBM Systems Director Server attempts to verify the credentials againstswitch.

When all the access types are not in the Full Access state, the switch state remainsPartial 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 FullAccess state, check to see if a switch vendor plug-in is required. For detailedinformation, see “Downloading and activating BladeCenter I/O module plug-ins.”

Troubleshooting and support 163

The server reports that "Power off and Restart" wassuccessful, but it was not

Running "Power Off and Restart" against a server managed endpoint reports that itwas successful, but the restart did not happen.

Problem

Instead of turning off the server and restarting, the operating system is promptingthe user to decide whether to let the server restart. This error is seen on serverswith the RH5.x Linux operating system installed.

Investigation

Determine whether the operating system is showing a prompt that requires userinput.

Explanation

The Integrated Management Processor (iMM) signals the operating system to shutdown and then assumes that the operating was shut down. However, if theoperating system is configured to prompt the user, then it does so and waits forthe user's input. This setting lets a user ensure that the server is not turned off orrestarted by accident.

Resolution

If this behavior is configured on the operating system but is not desired, changethe 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.

The System Identification menu options are not availableThis problem affects resources of type Server.

Problem

When working with a resource, the System Identification task is not available onthe pop-up menu and the Actions menu or the System Identification task does notprovide 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 areaffected:– Remote Supervisor Adapter

164 IBM Systems Director Troubleshooting and Support Guide

– 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 accessComplete 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 isavailable on the menu.

For an unresponsive processorFor the service processor, make sure that the applicable device driver andany other required software is installed. For detailed information, see“Service processor is unresponsive.”

Two different managed operating systems have the sameUUID after moving a blade system board to a different bladeslot

This problem affects a blade server that is managed by IBM Systems Director.

Problem

Two managed operating systems are associated with a single managed server,where both operating systems have the same universally unique identifier (UUID).

Explanation

IBM Systems Director uses the UUID of the system board as the UUID value of theassociated operating system.

For example, assume that a blade server in slot A was already discovered. Theblade system board in slot A is then moved to slot B, and a different system boardis placed into slot A. After completing these example actions, discovering theoperating system associated with the blade server now in slot B will lead to theproblem described in this topic.

Resolution

To resolve the problem, use the IBM Systems Director Web interface to rediscoverthe affected blade servers:1. Delete the managed server for the affected BladeCenter chassis.2. Delete the two affected managed operating systems.3. Delete the managed server to which the deleted operating systems were

associated.4. Rediscover the BladeCenter chassis, then successfully request access to it.5. Rediscover both operating systems that you want to manage, then successfully

request access to each of them.

Troubleshooting and support 165

Service processor is unresponsiveThis problem affects the Remote Supervisor Adapter, the Integrated ManagementModule, the Integrated Management Module II, and the IPMI baseboardmanagement 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, Remote Supervisor Adapter, Integrated Management Module, andIntegrated Management Module II models:

Make sure that the port settings for the service processor are correct. Formore information, see “Preparing firewalls and proxies for IBM SystemsDirector” in the IBM Systems Director Planning, Installation, and ConfigurationGuide for your system.

For Remote Supervisor Adapter models:

v Make sure that the affected system has a Remote Supervisor Adapterinstalled. Inspect the server to make sure that a Remote SupervisorAdapter is in its slot.

v Make sure that the Remote Supervisor Adapter is in the correct slot. Formany servers, the Remote Supervisor Adapter must be installed in aspecific slot. See the documentation for the server model to determinethe required slot.

v Make sure that the Remote Supervisor Adapter has power. The RemoteSupervisor Adapter requires its own power and it is separate from theserver power supply.

v Make sure that the correct firmware is installed. The Remote SupervisorAdapter firmware is specific to operating systems and server models. Ifthe installed firmware is for the correct operating system and servermodel, make sure that the firmware is at the latest level.

v Make sure that the device driver is installed and that it is the correctdevice driver is active.

v Make sure that the Remote Supervisor Adapter is correctly cabled foryour network configuration.

v Make sure that the Remote Supervisor Adapter is correctly configuredfor your network.

For DHCP Make sure that the adapter is configured touse DHCP.

For static IP addresses Make sure that the adapter is configured touse an IP address within the correct subnet.

v For the Remote Supervisor Adapter II, if the USB cable is required, makesure that it is attached correctly to a USB port. See the RemoteSupervisor Adapter documentation for information about this USB cable.

v Make sure that the Remote Supervisor Adapter is configured for thecorrect operating system. If the system is running Linux, set the RemoteSupervisor Adapter operating system setting to Linux; otherwise, set it toOther.

166 IBM Systems Director Troubleshooting and Support Guide

For BMC:

v Determine whether the affected server has a Remote Supervisor Adapterinstalled as well. If a server has both a Remote Supervisor Adapter anda BMC, IBM Systems Director ignores the BMC.

v (For systems that run Linux or Windows) Make sure that the devicedriver is installed, that it is the correct device driver, and that it is active.For detailed information, see “Preparing to manage service processorswith 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. Therequired files are server-specific. For detailed information, see “Preparingto manage service processors with IBM Systems Director”in the IBMSystems Director Planning, Installation, and Configuration Guide for yoursystem.

v (For in-band communication) View the install_root\cimom\logs\ibm-ipmi.log file, where install_root is the root directory of your IBM SystemsDirector installation. Note that this path uses the backslash (\) to delimitthe directory; depending on the system that you are using, you might berequired to enter the path using the forward slash (/). If this file is notpresent or the log entries are out of date, then no communicationbetween IBM Systems Director and the BMC occurred. This file logs anyerrors associated with loading or communicating with the IBM MappingLayer or IPMI device driver.

v (For out-of-band communication) Turn on ASM library logging to logcommunication with the service processor. To do so, complete thefollowing steps:1. Go to install_root\lwi\bin; where install_root is the root directory of

your IBM Systems Director installation. Note that this path uses thebackslash (\) to delimit the directory; depending on the system thatyou are using, you might be required to enter the path using theforward slash (/).

2. Run the following command on the IBM Systems Director Server:– If IBM Systems Director Server is installed on Windows:

lwilog -addlogger -name com.ibm.sysmgt.services.hcpcomlib \-level FINEST

– If IBM Systems Director Server is installed on any other operatingsystem:./lwilog -addlogger -name com.ibm.sysmgt.services.hcpcomlib \-level FINEST

For Integrated Management Module and Integrated Management Module IImodels:

v Make sure that the affected system has an Integrated ManagementModule or an Integrated Management Module II installed. Inspect theserver to make sure that an Integrated Management Module or anIntegrated Management Module II is in its slot.

v Make sure that the Integrated Management Module or the IntegratedManagement Module II is in the correct slot.

v Make sure that the correct firmware is installed.v Make sure that the device driver is installed, that it is the correct device

driver, and that it is active.

Troubleshooting and support 167

v Make sure that the Integrated Management Module or the IntegratedManagement Module II is correctly cabled for your networkconfiguration.

v Make sure that the Integrated Management Module or the IntegratedManagement Module II is correctly configured for your network. ForDHCP networks, make sure that the Integrated Management Module orthe Integrated Management Module II is configured to use DHCP. Forstatic IP addresses, make sure that the Integrated Management Moduleor the Integrated Management Module II is configured to use an IPaddress within the correct subnet.

Network management troubleshootingThis section provides information for specific problems and workaroundsassociated with Network Management in the IBM Systems Director environment.

Cannot view configuration of some switchesAn error is displayed when attempting to view the configuration of a switch that isnot a supported switch.

Problem

Unable to use the System Configuration > Current Configuration task on switchthat is not a supported switch to view switch configuration information. When thetask is selected, the following error is displayed:ATKNAV019I

There was a problem retrieving the requested data set, and you have been redirectedto 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 youhave been redirected to the home data set. See the logs for details.

Explanation: A data set could not be retrieved using the parametersspecified 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 isactive). The default location of the log files depends on the operating systemon which the product is installed. The following list provides the defaultlocation associated with each operating system.

AIX: /opt/ibm/director/lwi/logsLinux: /opt/ibm/director/lwi/logsWindows: root\lwi\logs, where root is the directory where the product is

installed. The default installation directory isc:\Program Files\IBM\Director.

If the problem persists, contact your next level of support or yourservice representative.

Investigation

Check the list of supported hardware for IBM Systems Director NetworkManagement. This problem will occur on switches that are listed as supported forNetwork Management function but not supported for configuration manager.

168 IBM Systems Director Troubleshooting and Support Guide

Explanation

If you attempt to start a configuration manager task on a switch that is notsupported by configuration manager, this error will occur.

Resolution

You cannot use configuration manager to view the configurations of switches thatare not supported by configuration manager. To manage configuration of switchesnot supported by configuration manager, launch a web interface to the switch anduse the switch's native configuration interface instead.

Cannot view network interface cardsThis problem affects the Network Management function.

Problem

After you install a IBM Systems Director upgrade, inventory collection displays abase board but does not display network interface card (NIC).

Resolution

Network Management in IBM Systems Director can only collect network interfacecard inventory for NICs that are part of a discovered BladeCenter chassis. This is aknown limitation.

To collect inventory for NICs that are assigned to a BladeCenter chassis, completethe 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 pagemay not display correct view

On first use, the pie chart on the Network Management summary page may notdisplay the correct view. This problem affects IBM Systems Director version 6.1.1and later versions.

Problem

After installing IBM Systems Director , the first time the user goes to the NetworkManager summary page, clicking on the pie chart may simply refresh the currentpage instead of going to the page displaying the discovered resources in a table. Inaddition, immediately after a device moves to warning or critical state, clicking theassociated status portion of the pie chart may not show the correct view of devicesin warning or critical state.

Resolution

Close the Network Management summary page and reopen it. Select the pie chartagain to display the discovered resources table or the appropriate view ofdiscovered resources or resources in warning or critical state.

Troubleshooting and support 169

IBM Systems Director Server sends unwanted or unexpectedmulticast packets

This problem affects users who do not want IBM Systems Director Server to sendunwanted or unexpected multicast or broadcast packets to Common Agentmanaged systems.

Problem

IBM Systems Director Server often uses the service location protocol (SLP) to sendmulticast packets to and receive multicast packets from registered listeners on thenetwork. If a user does not want to experience or detect unplanned multicastpackets, the amount of IBM Systems Director multicast traffic must be reduced.

Resolution

To significantly reduce multicast traffic caused by IBM Systems Director on thenetwork, complete the following steps:

CAUTION:Making the following changes might have unintended consequences. Forexample, after making the following changes, discovery processes (includingGetting started discovery and some default discovery profiles) cannotsuccessfully use multicast or broadcast to discover resources.

1. On the IBM Systems Director Server, make the following edits toinstall_root\data\slp.prop, where install_root is the root directory of your IBMSystems Director installation. Note that this path uses the backslash (\) todelimit the directory; depending on the system that you are using, you mightbe required to enter the path using the forward slash (/).active.da.discovery.interval=0passive.da.discovery=falsebroadcast=falsemulticast=false

2. Restart the IBM Systems Director Server. For instructions, see “Restarting IBMSystems Director Server”.

3. On the Common Agent managed system, create a file called slp.prop underinstall_root\agent\runtime\agent\subagents\director\ipc\data, whereinstall_root is the root directory of your Common Agent installation. After youcreate the file, add the following lines:active.da.discovery.interval=0passive.da.discovery=falsebroadcast=falsemulticast=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 stopinstall_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)

170 IBM Systems Director Troubleshooting and Support Guide

Completing the previous steps significantly reduces IBM Systems Directormulticast traffic.

Delay in threshold page reflecting exceeded thresholdWhen a threshold is exceeded, causing a device to move into warning or criticalstate, 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 NetworkManagement.

Problem

When you set a threshold on a monitor, and a device exceeds the threshold, it maytake over a minute for the threshold page to reflect the warning or critical state ofthe device.

Explanation

When a threshold is exceeded, it may take over a minute for the threshold page toreflect the status of the device. The monitor page will correctly reflect the status ofthe device.

Resolution

Wait for the threshold page to display the correct status, or view the status on themonitors page.

Duplicate network monitor thresholdsDuplicate 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.

Offline network interface card reports incorrect statusThis problem affects network interface cards that have a bonded interface and areinstalled 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 aWindows operating system and that has a bonded interface sometimes does notreport status correctly. When the NIC cables of both the bonded interfaces areunplugged, the NIC reports a status of "NIC has switched over" instead of "NICoffline." When the same NIC comes back online, the NIC reports a status of "NIChas switched back."

Troubleshooting and support 171

Resolution

This behavior is a known limitation.

IBM Power Systems managementThis section provides information about problems for the IBM Power Systemsmanagement management plug-in.

Using IBM i resources with an IBM Systems Director ServerThis issue affects IBM i systems.

Getting started1. 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 theIBM Systems Director agent, IBM Systems Director Navigator for IBM ifunctions, software inventory and IBM Systems Director support for IBM iGroup and cumulative program temporary fixes (PTFs).

v Platform Agent (formerly Level 1) provides agentless functions, CommonInformation Model (CIM) events and monitoring, and additional hardwareinventory. Starting with Systems Director version 6.3, Platform Agentsupports monitoring IBM i message queues.

v IBM Systems Director Common Agent for IBM i provides agentless andPlatform Agent functions. IBM Systems Director Common Agent for IBM ialso provides capabilities such as file transfer.

2. After you decide which level of agent is needed, reference the requiredsoftware and install documentation for the agent.

Notes:

v Platform Agent support is provided with the IBM i Licensed ProgramProduct.– On IBM i 5.4, use 5722UME V1R2– On IBM i 6.1 and 7.1, use 5770UME V1R3

v IBM Systems Director Common Agent for IBM i can only be installed on IBMi 6.1 and later releases.

Requesting access to IBM Systems Director Common Agent forIBM i

The user id that requests access to IBM Systems Director Common Agent for IBM imust have these special authorities:v *ALLOBJv *AUDITv *IOSYSCFGv *JOBCTLv *SAVSYSv *SECADMv *SERVICEv *SPLCTL.

172 IBM Systems Director Troubleshooting and Support Guide

Those authorities are provided if the userid has USRCLS = *SECOFR and SPCAUT= *USRCLS and the IBM i default values for those authorities have not beenchanged.

Starting IBM Systems Director services on an IBM i system1. 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 thosestarted. Refer to IBM i documentation for instructions to configure services toautostart during a system power up. Some of the TCP servers that you mightneed 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 CIMmonitors

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 collectionservices, 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 Description Supported IBM i releasesRequired IBM iproducts-(not all inclusive) Configure/start

Agentless (Level 0) SSH Any 57**SC1 base and option 1(ssh) for the OS versionbeing used.

v IBM i 6.1 and later:strtcpsvr *sshd

v IBM i 5.4 see: OpenSSH

Platform Agent (Level 1)1 SSH, CIM and IBM SystemsDirector specificregistration. This requiresSLP.

5.4, 6.1, 7.1 Level 0 products

CIM / Pegasus PTFs:v 5770UME V1R3M0 (i 6.1

and 7.1)v SI41540v SI41685orv 5722UME V1R2M0 (i 5.4)v SI41038v SI33622SLP (Base OS) PTFs:v i 7.1 5770SS1

– SI42321– SI39065

v i 6.1: 5761SS1– SI42320– SI39017

v i 5.4: 5722SS1– SI39110– SI41129

v Level 0 startedv strtcpsvr *slpv strtcpsvr *cimomv for monitoring, collection

must be started :– CFGPFRCOL– INTERVAL(5.0)

CYCITV(01)– ENDPFRCOL– STRPFRCOL

CYCCOL(*YES)

Troubleshooting and support 173

Table 6. IBM i resource levels (continued)

IBM i resource level Description Supported IBM i releasesRequired IBM iproducts-(not all inclusive) Configure/start

Common Agent Services(CAS)--IBM i Agent

IBM Systems DirectorCommon Agent for IBM i

6.1, 7.1 v Level 0 productsv Level 1 5770UME

V1R3M0v 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 startedv Level 1 startedv STRTCPSVR

SERVER(*HTTP)HTTPSVR(CAS)

v To stop:– ENDTCPSVR

SERVER(*HTTP)HTTPSVR(CAS)

1. For the most current IBM i PTF information, refer to the CIM information inthe Software Knowledge Base.

Related information:

IBM System i and i5/OS Information Center

Remote access troubleshootingThis section provides information about problems and workarounds related to theremote access manager plug-in.

File Management does not display files with Chinesecharacters in the file name if these files were transferred witha tool other than IBM Systems Director File Management

Problem

When you transfer a file with a name that contains some or all Chinese charactersusing a tool other than the File Management task of IBM Systems Director, the filename is not listed in the Target File System list of the File Management page.

Resolution

Transfer these files using the File Management task of IBM Systems Director.

File Management does not support certain characters in filenames when using the rename function

File Management does not support these characters in file names: '*', '?',or '|'(asterisk, question mark, vertical bar) when the rename function is used.

Problem

If you try to rename a file or directory with a new name that contains specialcharacters: '*', '?',or '|' from within the File Management facility, an error isdisplayed. The file or directory will not be renamed.

Resolution

Delete all the special characters from the file or the directory name, and then youcan rename it successfully.

174 IBM Systems Director Troubleshooting and Support Guide

Remote command line prompt on a Windows 2003 CommonAgent managed system does not have working scroll bars

This problem affects users of Remote command line on a Windows 2003 CommonAgent managed system.

Problem

The Remote command line prompt on a Windows 2003 Common Agent managedsystem may not have working scroll bars. In addition, you might be unable toresize the window, which will disable you from being able to return to the promptafter you type the first command. Finally, the entire Remote command promptwindow and the launched task window can freeze.

Explanation

Windows 2003, 64 bit edition, contains an Enhanced Security Configuration toprevent 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. Deselect the check box next to it and complete the removal process.

Unable to export file using Microsoft Internet Explorer 9This problem affects users attempting to export a file using Microsoft InternetExplorer 9.

Problem

If the user tries to export a file from the IBM Systems Director and is prompted tosave with a partial URL string rather than a valid filename, the export will notwork. This is due to a Microsoft Internet Explorer 9 security setting.

Explanation

In Microsoft Internet Explorer 9, if Do not save encrypted pages to disk is selectedyou will not be able to download the file.

Resolution

To deselect Do not save encrypted pages to disk follow these steps:1. In Microsoft Internet Explorer, go to Tools > Internet Options.2. Select the Advanced Options tab.3. In the settings window, use the scroll bar to locate Do not save encrypted

pages to disk. It will be found under Security.4. Uncheck the box next to it and click OK.

Troubleshooting and support 175

System z managementThis section provides information about problems for the IBM System zmanagement plug-in.

Discovery of z/VM managed resources does not functioncorrectly

This problem affects managed resources hosted by the z/VM® operating systemand occurs during the discovery process.

Problem

You cannot discover any managed resources that are hosted by the z/VMoperating 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

pointv A firewall is blocking communication to the IBM z/VM Manageability Access

Point Agentv The Platform Agent or IBM z/VM Manageability Access Point Agent is not

installedv The CIM server is not runningv The z/VM Systems Management API server is not working or not able to

communicate with the IBM z/VM Manageability Access Point Agentv 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 IBM

z/VM Manageability Access Point Agent. For more information, see“Supported operating systems”.

2. Ensure that there are no firewall problems.3. Ensure that Platform Agent is running by issuing the following set of

commands (Platform Agent 6.3 and later only):/opt/ibm/icc/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grepLinux_ComputerSystem

/opt/ibm/icc/bin/cimcli ei CIM_ComputerSystem -niq --timeout 300 | grepIBMzVM_HostComputerSystem

4. 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/ibmpawatchdogd stop (Platform Agent 6.3 and later only)/etc/init.d/cimserverd stop/etc/init.d/tier1slpinst stop/etc/init.d/cimlistenerd stop/etc/init.d/paslpd stop (Platform Agent 6.3 and later only)

b. Start Platform Agent by typing the following commands and then pressingEnter:

176 IBM Systems Director Troubleshooting and Support Guide

/etc/init.d/paslpd start (Platform Agent 6.3 and later only)/etc/init.d/cimlistenerd start/etc/init.d/tier1slpinst start/etc/init.d/cimserverd start/etc/init.d/ibmpawatchdogd start (Platform Agent 6.3 and later only)

5. Ensure that the SLP daemon is running by issuing the following command(Platform Agent 6.3 and later only):/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.6. Select from the following options:

a. If Platform Agent is not running, go to step 7.b. If Platform Agent is running, go to step 8.

7. Ensure that Platform Agent is installed by checking for the version.lv1 file in/opt/ibm/platform.If Platform Agent is not installed, install it and IBM z/VM ManageabilityAccess Point Agent. Then, try to discover the managed resources again. Forinstallation instructions, see “Installing Platform Agent” and “Installing IBMz/VM Manageability Access Point Agent”. If you are still unable to discoverthe managed resource, go to step 9.If Platform Agent is installed, go to step 8.

8. Ensure that IBM z/VM Manageability Access Point Agent is installedsuccessfully by checking for the version.zvmmap file in the /opt/ibm/zvmmapdirectory.

Note: An alternate method of ensuring that the IBM z/VM ManageabilityAccess Point Agent is installed is to run the following command for PlatformAgent 6.3 and later:/opt/ibm/icc/bin/cimcli ei -n root/ibmsd IBMPSG_DirectorAgent | grep Version

If IBM z/VM Manageability Access Point Agent is not installed, install it andtry 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 9.

9. Ensure that z/VM Systems Management API server is working. Type thefollowing command and press Enter:/opt/ibm/zvmmap/bin/testSMAPI

If the z/VM Systems Management API server is working, you will see resultsthat 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 SMAPIThe directory for OPERATOR contains 13 records

An error message might be displayed. Read the following information toidentify possible error messages and how to resolve them:

Troubleshooting and support 177

Table 7. Error messages and resolutions

Error message Resolution

Unable to obtain socket Ensure that the kernel module af_iucv wasproperly loaded into the Linux system. Tocheck if it was loaded, run the followingcommand:

lsmod |grep af

If the module was properly loaded, runningthe command will produce results similar tothe following output:

af_iucv 150624 0iucv 111192 1 af_iucv

If you do not receive this output, themodule was not loaded and you need toperform the following steps:

1. Run the following command to load themodule:

modprobe af_iucv

2. Configure the module to load every timethe 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 thefile:

chmod +x /etc/rc.modules

Connection refused Ensure that the z/VM Systems ManagementAPI file VSMWORK1 AUTHLIST contains theLinux IBM z/VM Manageability AccessPoint Agent user ID.

Connection retry exceeded Options:

v Wait until the z/VM SystemsManagement API server is less busy, andtry the task again.

v Ensure that the IUCV ALLOW statementis in the VSMREQIU directory.

v Go to step 10a on page 179.

Other errors Go to step 10a on page 179.

178 IBM Systems Director Troubleshooting and Support Guide

If you are unable to resolve the errors, contact your IBM servicerepresentative.If the z/VM Systems Management API server is still not working, go to step10.

10. Ensure that the z/VM Systems Management API user IDs are running on thez/VM system.

Note: If the VSMGUARD virtual machine is configured for z/VM SMAPI,specify that instead of VSMWORK1 in the following commands.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 pressEnter:#CP XAUTOLOG VSMWORK1

VSMWORK1 will force off and automatically log on the other servers itneeds.

b. Run a query to determine whether the required z/VM SystemsManagement API user IDs are running. Log on to the z/VM host asMAINT, type the following command, and press Enter:QUERY NAMES

Verify that the following z/VM Systems Management API user IDs arerunning:v VSMREQIN - DSCv VSMREQIU - DSCv VSMWORK1 - DSCv VSMWORK2 - DSCv VSMWORK3 - DSCv 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 yourIBM service representative.For more information about the z/VM Systems Management API andDirMaint, see the following documentation:v z/VM Systems Management API documentation:

– Systems Management Application Programming SC24-6122v 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 ProcessCount on Linux on System z

This problem affects the Linux on System z that has Platform Agent installed.

Troubleshooting and support 179

Problem

When you view the Common CIM Monitors for the Linux on System z that hasPlatform Agent installed, you notice that the values for CPU utilization andprocess count are not correct.

Explanation

This problem is a known limitation of IBM Systems Director.

Job status for inventory collection on IBM z/VM ManageabilityAccess Point Agent is Complete with Errors

This problem affects the IBM z/VM Manageability Access Point Agent duringinventory collection.

Problem

When you use the Collect Inventory task to collect inventory data on the IBMz/VM Manageability Access Point Agent, the job status for inventory collection isComplete with Errors.

Explanation

The Collect Inventory task for the IBM z/VM Manageability Access Point Agentcan take 40 minutes or more to complete. However, the Collect Inventory tasktimes out after 20 minutes, the default timeout value.

Resolution

Increase the timeout value for the Inventory Collection task, by completing thefollowing 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 onSystem z resources that have been discovered during system discovery. In mostcases, 180 minutes is a sufficient length of time to collect inventory on theresources associated with the IBM z/VM Manageability Access Point Agent.

3. Restart the IBM Systems Director Server.

Storage systems management troubleshootingThis section provides information about problems and workarounds related to thestorage systems management plug-in.

Cannot start an IBM DS Storage Manager with version laterthan 10.6.x.x

Only version 10.60.g5.16 or earlier is supported. If you already downloaded a laterversion of IBM DS Storage Manager and cannot start it, try this procedure.

180 IBM Systems Director Troubleshooting and Support Guide

Resolution

For later versions of IBM DS Storage Manager, the binary names might havechanged. Try the following steps to solve this problem:

On Microsoft Windows systems:

1. Navigate to the directory that contains the file DS Storage Manager 10Client.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 10Client.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 byusing this command:ln -sf /opt/IBM_DS4000/client/SMclient /usr/bin/SMclient

Cannot start DS storage manager when using WindowsInternet Explorer 8

You need to change the Internet Explorer security settings before launching StorageDS Storage Manager.

Details

The default configuration of Internet Explorer 8 disables the "Automatic promptingfor file downloads" option.

Resolution1. From Internet Explorer, open Tools > Internet Options > Security > Custom

Level.2. Scroll down to the Downloads section. Under the Automatic prompting for

file downloads option, select Enable and click OK.3. Restart Internet Explorer.4. Retry launching the task.

Cannot access PlatformAgentSubagent SMI-S for IBM SASRAID Controller Module

IBM Systems Director 6.2 Platform Agent has been installed, but now you cannotaccess PlatformAgentSubagent SMI-S for IBM SAS RAID Controller Module.

Problem

You try to discover IBM SAS RAID Controller Module SMI-S provider by usingSLP discovery or SMI-S discovery. The request to unlock fails.

Resolution

Ensure that the installed versions of Platform Agent and the SMI-S provider arecompatible. The following combinations are compatible:

Troubleshooting and support 181

v IBM Systems Director Platform Agent 6.2 and IBM SAS RAID Controler ModuleSMI-S Provider R2.1 (version 4.xx)

v IBM Systems Director Platform Agent Core Services 5.20.31 and IBM SAS RAIDControler Module SMI-S Provider R1 (version 2.99)

DS 3000/4000/5000 proxy provider configuration causesprovider to fail

When trying to add a device into a DS device that is Chromium (06.60) and 06.12firmware (CFW) versions, the target DS3000/4000/5000 provider might crash.

Problem

When configuring the DS3000/4000/5000 provider by adding a device, the usercan input both the primary and secondary controller's IP addresses. When thetarget device is of the firmware level specified above, entering both values willcrash 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 IPaddress. Do not specify the secondary controller's IP address.

Additional information

This problem is only observed when the DS device is Chromium (06.60) and 06.12firmware (CFW) versions. For DS devices at other firmware levels, this problemwill not happen.

Unable to discover an SMI-S providerYou have installed an SMI-S Provider and IBM Systems Director is not discoveringit.

Problem

In the System Discovery screen, you insert the IP Address of an SMI-S Provider onyour network and wait until discovery finishes. At the end of the process, IBMSystems Director does not find your system.

Explanation

SMI-S Discovery uses the Service Location Protocol to find SMI-S systems on yournetwork. 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 orusing 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, whichvaries by provider.

182 IBM Systems Director Troubleshooting and Support Guide

To run an SLP query by hand, run this command for Linux:

Platform Agent 6.2.1/opt/ibm/icc/bin/slptool options

Where options are the options that you specify based on the informationin 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 IPaddress of your resource.

If the SMI-S provider and the IBM Systems Director Server are on differentsubnetworks, you canv 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 thenetwork where the SMI-S provider resides.

After requesting access to an SMI-S provider, no storagesystems or switches are displayed

You discovered a system that you know is one of your SMI-S providers, and afterrequesting 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 Discoveryfailure.

Investigation

If the system you unlocked is not in the Storage Systems > SMI-S Providersgroup, IBM Systems Director did not recognize it as a system having an SMI-Sprovider.

Resolution

See the topic 'Unable to discover an SMI-S provider' for storage discoverytroubleshooting.

If you choose to use a Directory Agent, you need to configure it in the networkwhere the SMI-S provider resides.

SMI-S provider configuration fails to add a storage deviceWhen configuring an SMI-S provider, storage devices are not added.

Troubleshooting and support 183

Problem

When you try to add a storage device with an SMI-S provider, the operation failsafter clicking OK on the Add Storage Devices page.

The storage system will not be added, and you will stay on the same page, wherea 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 thisstatus is not reflected immediately in the IBM Systems Director Web interface.You can do this by selecting the storage system and clicking Actions > Verifyconnection.

2. If you are using manual mode, verify that the IP addresses for both theprimary and secondary controllers are correct. You can try running a pingcommand for the controllers, or check if the controllers can be resolved fromyour server system.

3. If you are using manual mode and you typed the correct credentials but the IPaddresses for the controllers were incorrect, you will receive this error message:"An unexpected error occurred while performing the selected operation". Verifythat the IP addresses for the controllers are correct.

4. Another reason for this failure is that you might be providing the wrongcredentials for the storage device. Check the error message displayed in theIBM Systems Director Web interface, and if you find that it is a security-relatedproblem, confirm that you have access to the storage system with the givencredentials, and that they are typed correctly.

5. Verify that the storage device you are trying to add can be managed by theSMI-S provider that you have chosen. SMI-S provider configuration will runonly for SMI-S SAS RAID Controller Module providers.

6. If the SMI-S provider is hosted by a Windows system, make sure that theselected protocol is http. You select the protocol in the Discovery Profile wizardfor the SMI-S provider. The SMI-S provider for Windows does not supporthttps protocol properly.

SMI-S provider configuration fails to remove a storage deviceWhen configuring an SMI-S provider, storage devices are not removed.

Problem

This is from the SMI-S Provider Configuration page, which is launched when youselect a system that is an SMI-S provider. When you try to remove a storage devicecontrolled by the SMI-S provider, the operation fails after selecting the device andclicking Actions > Remove.

The storage system will not be removed, and you will remain on the same IBMSystems Director Web interface page where an error message is displayeddescribing the problem.

This problem is independent of the web browser that you use.

184 IBM Systems Director Troubleshooting and Support Guide

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 thisstatus is not reflected immediately in the IBM Systems Director Web interface.You can do this by selecting the storage system and clicking Actions > Verifyconnection.

2. See if the storage device has been removed by other means, but it has not beenreflected in the IBM Systems Director Web interface. From the same VerifyConnection task mentioned in the previous step, check the Query for VitalProperties box. If the storage device has been removed, the next time it will notbe displayed n the IBM Systems Director Web interface.

3. In order to remove devices attached to a RAID controller, information about theRAID 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 SASRAID Controller Module on additional systems completes witherrors

The agent install of the PlatformAgentSubagent IBM BladeCenter SAS RAIDController 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 hasone of these operating-system dependent names:v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0

Linuxv 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 thisSMI-S provider on a system that does not have a Platform Agent managed systeminstalled. However, this configuration will not work properly.

Explanation

For the configuration to function properly, IBM Director 5.20.3 Level-1 agent mustbe on the system prior to running the agent installation task for thePlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0.However, due to a limitation of the agent installation task, there is no way toprevent the user from install it to a system that does not have minimum of IBMDirector 5.20.3 Level-1 agent.

Resolution

Install IBM Director 5.2.0.3 Level-1 agent prior to running the agent installationtask for the PlatformAgentSubagent IBM BladeCenter SAS RAID ControllerModule 6.1.0.

Storage events not being displayed in the event logYour storage device is failing, but IBM Systems Director is not displaying events.

Troubleshooting and support 185

Problem

You know that your storage device is having problems, yet you see no events inIBM Systems Director.

Resolution

In order to receive events in IBM Systems Director, you need to have discoveredthe SMI-S provider and have it in an unlock state. Event subscriptions occasionallybecome 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 isselected, and click Verify. The subscriptions should be updated periodically, butthis is a quick way of updating them.

Unable to display a topology map of a SANThere are discovered devices from a SAN, but you cannot see the links betweenthem.

Problem

In IBM Systems Director, you have discovered all of your SAN devices, yet whenyou 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 ischanged in an IBM BladeCenter system

This problem affects SAN configuration with IBM BladeCenter systems.

Problem

After you deploy a SAN configuration template, then remove or replace a blade toan IBM BladeCenter chassis, the SAN configuration profile of this blade is notupdated on storage related to this chassis.

Explanation

The deploy function of SAN configuration template to IBM BladeCenter systemfunctions to get the SAN configuration profile of blades and set the target blade. Ifyou did not selected the blade in the SAN configuration template and then deploythe template, the SAN configuration profile will not be saved, and SANconfiguration profile of the blade will not be replaced.

186 IBM Systems Director Troubleshooting and Support Guide

Resolution

Make sure that you selected all appropriate blade, and deployed the SANconfiguration template to the IBM BladeCenter system.

Replace and remap task fails with an IBM BladeCenter S SASRAID Controller Module for a blade whose host name is morethan twelve characters in length

The replace and remap task fails with an IBM BladeCenter S SAS RAID ControllerModule 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 RAIDController Module after inserting the new blade.

Problem

When you use the replace and remap task on an IBM BladeCenter S SAS RAIDController 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 BladeCenterS SAS RAID Controller Module. It is currently a firmware limitation. The physicallimit in firmware is 24 characters, where the first twelve are available for userdefinition. They are limited to alphanumeric characters and the underscorecharacter.

Resolution

Use this command to change blade&apos;s host name to twelve or fewercharacters: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 charactersconsisting of letters, numbers, or underscores, and where blades display name isthe current value of the blade&apos;s host name.

iSCSI configuration accepts incomplete IPv4 format addressesWhy IPv4 address formats such as '1', '1.', '1.2', and '1.2.3' are valid in iSCSIconfiguration.

Problem

When you create an iSCSI configuration template, you must provide some IPaddresses. If you type an incomplete string by mistake, you do not receive an errormessage.

Troubleshooting and support 187

Investigation

Textual representation of IPv4 address used as input to methods takes one of thefollowing forms:

d.d.d.dd.d.dd.dd

When a four part address is specified, each is interpreted as a byte of data andassigned, 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 bitquantity and placed in the rightmost two bytes of an IPv4 address. This makes thethree part address format convenient for specifying Class B network addresses as9.186.96.

When a two part address is specified, the rightmost part is interpreted as a 24 bitquantity and placed in the rightmost three bytes of an IPv4 address. This makesthe two part address format convenient for specifying Class A network addressesas 9.186.

When an address consisting of only one part is specified, the value is storeddirectly 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 IBMBladeCenter after access to the Advanced ManagementModule

This problem affects SAS zone configuration in IBM BladeCenter systems.

Problem

When you try to deploy a SAS Zone configuration template to an IBM BladeCenterchassis, the deploy fails, although access request to the Advanced ManagementModule of the IBM BladeCenter chassis is successful. After discovery and accessrequest to the IBM BladeCenter chassis are done, there will be a SAS switchdisplayed in the resource group. The SAS Zone configuration template is supposedto apply to a IBM BladeCenter chassis or SAS switch.

Resolution

Request access to the SAS switch first when you want to deploy a SAS Zoneconfiguration template, or configuration plan that contains a SAS Zoneconfiguration template, to the SAS switch.

No predefined SAS zone configuration when there is only oneSAS switch, and it is on I/O Module 4 on an IBM BladeCenterS system

This problem affects SAS zone configuration in IBM BladeCenter systems.

188 IBM Systems Director Troubleshooting and Support Guide

Problem

When you create a SAS Zone configuration template with just one SAS switch onI/O Module 4, a warning message is issued: DNZCP2726E - I/O Module 4 doesnot support predefined configuration. In a single SAS module configuration, theSAS module must be placed in I/O Module 3 in order to access predefinedconfigurations.

You will see that there is no predefined SAS zone configuration stored in theconfiguration template.

Resolution

The predefined SAS zone configuration is saved in the SAS switch and is set forthe recommended configuration. On IBM BladeCenter S systems, we suggest that ifyou have only one SAS switch, to put it on I/O Module 3. There will be nopredefined SAS zone configuration for one SAS switch on I/O Module 4.

Mismatched configuration of two SAS switches on an IBMBladeCenter S system

This problem affects SAS zone configuration in IBM BladeCenter systems.

Problem

If you have two SAS switches on an IBM BladeCenter S system, and they havedifferent SAS zone configurations, there will be a warning message about thedifferent 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 mismatchedconfiguration can cause unexpected results.

Resolution

On IBM BladeCenter S systems, there are two storage modules. If there are twoSAS 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 configurationfor blades to external ports or disks. We suggest that have the same SAS zoneconfiguration on two SAS switches on one IBM BladeCenter S system.

Cannot view available storages when creating a logicalvolume in offline mode

This problem affects storage provisioning using configuration templates.

Problem

When you try to view logical volumes using the Storage provisioningconfiguration template, you might want to choose the target storage system byyourself, as opposed to allowing IBM Systems Director to make the choice. Butsometimes, IBM Systems Director fails to list available storage, so there are nostorage 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:

Troubleshooting and support 189

v On the Profile Properties page, select Operating System as the resource type andAll as the resource subtype.

v On the Protocol Selection page, select Storage Management InitiativeSpecification (SMI-S) Discovery.

v On the SMI-S Configuration page, select Direct connection, select the appropriatehardware type, and specify the IP address of the storage provider.

After saving the discovery profile, run system discovery using the profile, thenunlock the storage provider. If you see that the storage is shown in the ResourceExplorer page after unlocking the provider, you can then select this storage in theStorage provisioning configuration template.

Cannot get some properties of storage devicesThis problem affects storage provisioning using configuration templates.

Problem

When you try to choose logical volume allocation by yourself, you can see someproperties of the storage listed in the Logical Volumes page. But sometimes, someproperties 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 andconnection type for the storage, you need to collect inventory on the storage.

SAS Port panel launched from SAS switch is not correctWhen a Serial Attached SCSI (SAS) switch is selected, and SAS port information isdisplayed, 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 youare using for instructions.

190 IBM Systems Director Troubleshooting and Support Guide

IBM BladeCenter S SAS RAID Controller Module menu tasksare not displayed for an attached storage array (storagesubsystem)

IBM BladeCenter S SAS RAID Controller Module menu tasks are not displayed onthe storage array menus.

Problem

After discovering the SMI-S provider for the IBM BladeCenter S SAS RAIDController Module using SLP discovery, appropriate menus are not displayed. Theproblem 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 RAIDController Module is in the same subnet as the management server. If not, useSMI-S discovery instead of SLP discovery for this SMI-S provider.

IBM BladeCenter S SAS RAID Controller Module menu tasksfail for an attached storage array (storage subsystem)

IBM BladeCenter S SAS RAID Controller Module menu tasks are displayed on thestorage array, but they do not work properly.

Problem

After discovering the SMI-S provider for the IBM BladeCenter S SAS RAIDController Module using SLP discovery or SMI-S discovery, appropriate menus aredisplayed, but they have an incorrect domain. The problem can be seen with thissequence 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. Right click on an attached storage resource.4. Select System Configuration or System Status and Health.5. Select any storage-related task.6. 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.

Troubleshooting and support 191

A previously supported IBM BladeCenter S SAS RAIDController Module is no longer supported after installing IBMSystems Director 6.1.1.

An IBM BladeCenter S SAS RAID Controller Module that was discovered andsupported by IBM Systems Director 6.1 is no longer supported after installing IBMSystems Director 6.1.1 Platform Agent.

Problem

After installing IBM Systems Director 6.1.1, then manually installing PlatformAgent 6.1.1, a BladeCenter S SAS RAID Controller Module that was discoveredand supported by IBM Systems Director 6.1 is no longer supported. Installing IBMSystems 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 thatyou install on a remote system.

Cannot create RAID 0 level pools on certain LSI IRC devicesUsing the Create Volume wizard to create a RAID 0 level pool on an IntegratedRAID 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 withonly one (1) drive. To create a RAID 0 pool for an LSI 106x IRC device, you mustspecify at least two (2) drives to create a pool.

Capacity information is not correct for storage devicesThe capacity information displayed on the Local Storage row of the StorageManagement 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 0because of this limitation. The other rows (Network storage and IBM BladeCenterstorage) are correct.

Resolution

Use operating system utilities or storage management applications to determineusable and available storage capacity.

192 IBM Systems Director Troubleshooting and Support Guide

When managing an Integrated RAID Controller (IRC), incorrectcontroller device information is displayed.

Sometimes, when managing an Integrated RAID Controller (IRC) device, theinformation shown is incorrect.

Problem

When managing an Integrated RAID Controller (IRC) device, the interface displaysincorrect information.

Resolution

To ensure that the Storage Manager displays correct information for the IRC deviceyou are managing, verify that you have installed the latest driver levels for thatIRC. For more information about the latest drivers and firmware levels, access theWeb site for the device manufacturer.

Some menu options are missing for an Integrated RAIDController (IRC) device

Previously visible options under the menus System Configuration and SystemStatus and Health for an Integrated RAID Controller (IRC) device no longerappear.

Problem

The following options that appeared in the System Configuration or SystemStatus and Health menu for IBM Systems Director 6.1 for an Integrated RAIDController (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 thepreviously specified menu options associated with those tasks are no longeravailable.

Some ServeRAID MR controller devices not supported by IBMSystems Director 6.1.1

After installing IBM Systems Director 6.1.1 Platform Agent, some RAID devices areno longer supported.

Problem

After installing IBM Systems Director 6.1.1 Platform Agent, some RAID controllerdevices do not send alerts or health status and do not gather inventory.

Troubleshooting and support 193

Resolution

Use a combination of an IBM Systems Director agent and the supportedServeRAID manager extension from the following table.

Table 8. IBM Systems Director agent and ServeRAID manager extension combinations thatsupport specific RAID controllers

RAIDcontroller

PlatformAgent 6.1.1and later

IBM DirectorCore ServicesAgent,version5.20.31

IBM DirectorCore ServicesAgent,version 5.20.3

IBM DirectorLevel 2Agent.version 5.20.3

IBM DirectorLevel 2Agent,version 5.20.2

ServeRAID4H/4M/4L/4Mx/4Lx

Notsupported

Yes1 Yes1 Yes2 Yes3

ServeRAID 5i Notsupported

Yes1 Yes1 Yes2 Yes3

ServeRAID6i/6i+/6M

Notsupported

Yes1 Yes1 Yes2 Yes3

ServeRAID7k/7t

Notsupported

Yes1 Yes1 Yes2 Yes3

ServeRAID7e/8e

Notsupported

Yes1 Yes1 Yes2 Yes3

ServeRAID8k/8k-l/8i/8s

Notsupported

Yes1 Yes1 Yes2 Yes3

LSI1020/1030

Notsupported

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-IIdevices not supported by IBM Systems Director 6.1.1

Cannot use IBM Systems Director 6.1.1 Platform Agent to manage RemoteSupervisor Adaptor or Remote Supervisor Adaptor II devices.

Problem

After installing IBM Systems Director 6.1.1 Platform Agent, you can not manageRemote Supervisor Adaptor or Remote Supervisor Adaptor II devices.

Resolution

IBM Systems Director 6.1.1 Platform Agent does not support Remote SupervisorAdaptor or Remote Supervisor Adaptor II devices. Remote Supervisor Adaptor andRemote Supervisor Adaptor II devices work only with IBM Director Core Services,version 5.20.31.

194 IBM Systems Director Troubleshooting and Support Guide

Storage panel or Long Running Tasks panel fails whenmanaging ServeRAIDMR Controller or Integrated RAIDController (IRC) devices

After updating to IBM Systems Director 6.1.1 and working to manage either anIntegrated RAID Controller (IRC) or a ServeRAID MR controller, certain panels failand then always show an error.

Problem

After updating to IBM Systems Director 6.1.1, when managing an IRC device or aServeRAID MR Controller device, certain panels fail and then always show anerror.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 toalways display on the panel.

Resolution

The system configuration tasks for ServeRAID MR devices and IRC devices do notwork with older providers, even when using IBMDirector Core Services agent,version 5.20.31. However, tasks associated with basic discovery, inventory, andalerts do work correctly.

A pool with a RAID level of RAID10 on a ServeRAID MRController device can have a maximum of four drives

Volume pools with a RAID level of RAID10 created for ServeRAID MR Controllerdevices cannot contain more than four drives.

Problem

Using the Create Volume Wizard to create a pool with a RAID level of RAID10 fora ServeRAID MR Controller device fails when you specify more than four (4) diskdrives.

Resolution

It is a known limitation that a pool with a RAID level of RAID10 for a ServeRAIDMR device can contain a maximum of four disk drives.

Using tasks available on Storage panel for Integrated RAIDController (IRC) devices results in errors

After installing IBM Systems Director 6.1.1, some tasks on the Storage panel forIntegrated RAID Controller (IRC) devices result in errors.

Problem

After installing IBM Systems Director 6.1.1 Platform Agent, using most of the tasksavailable on the Storage panel results in errors.

Troubleshooting and support 195

Resolution

The Storage panel in IBM Systems Director 6.1.1 supports only two tasks for IRCdevices. Use only the following tasks that are supported for IRC devices: CreateVolumes and Delete Volume, both of which appear on the Volume tab. TheIntegrated RAID Controller does not support many other advanced functionsavailable for Storage Management in IBM Systems Director 6.1.1, including thefollowing: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 forIntegrated RAID Controller devices.

Controller error when starting a taskWhen launching a task against an AR/IR host with CAS agent installed, you mightget one of these controller errors:

GWMAR1020EUnable to retrieve controller information associated with host ip_address...

GWMAR0102WNo 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 andselect Credential.

3. A new table opens. Click Configure Credentials in the upper left corner of thetable. 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.

196 IBM Systems Director Troubleshooting and Support Guide

System status and health troubleshootingThis section provides information for specific problems and workaroundsassociated with the System status and health task.

LPAR life-cycle indications are missingIf logical partition (LPAR) life-cycle indications are not listed in the IBM SystemsDirector event log, you might need to update the Virtual I/O Server (VIOS) orIntegrated Virtualization Manager (IVM).

Problem

LPAR life-cycle indications (Create, Delete, Activate, and Shutdown) are not listedin the Systems Director event log, but Power on and Power off events are listed.

Explanation

If the VIOS or IVM fileset "ios.lparmgr.cim.rte" level is 6.1.4.0 or lower, SystemsDirector cannot receive LPAR life-cycle indications from VIOS or IVM.

Resolution

To determine the fileset level, run this command: lspp -l ios.lparmgr.cim.rte.

Example output:Fileset Level State Description

----------------------------------------------------------------------------Path: /usr/lib/objrepos

ios.lparmgr.cim.rte 6.1.6.15 COMMITTED IVM - CIM Providers

If the level is 6.1.4.0 or lower, update the VIOS or IVM to higher level. Forinstructions to update the VIOS or IVM, see the topic “Updating the VIOS”.Related tasks:

Updating the VIOS

Automation command does not show the interactive programwindow

This problem affects machines running the Windows 2008 operating system.

Problem

An interactive program is any program that is launched in a user interface windowand requires user intervention, for example notepad.exe. When you try to use thecommand automation task to run an interactive program on Windows 2008, theprogram is not launched as expected. However, the process related to thatinteractive program is still is displayed in the Windows task manager.

Explanation

The command automation task is intended for command line automation, whichincludes only those processes that terminate by themselves within a specified timeperiod and require no user intervention.

Troubleshooting and support 197

It is possible, though not supported, to use the command automation task tolaunch interactive programs. However, this is not even possible on Windows 2008.Windows 2008 has a new set of security considerations that come into effect andcause the interactive program window to not appear, though the process is listedas active and running in the Windows task manager. The processes are launched inthe service session (session ID 0), which is never a desktop session.

Resolution

Use a method other than the command automation task to launch interactiveprograms.

Cannot add selected resources to a monitor viewThis problem affects monitoring on any resource.

Problem

When you select resources on the Create View page to add to a monitor view, Addis 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 CPUUtilization, is selected. If you select any items that cannot be monitored, Addremains deactivated.

Resolution

Select a different resource to monitor.

Disk monitors does not display all folders under root pathThis problem affects managed systems that are running AIX, UNIX and Linuxoperating systems.

Problem

When creating or editing a monitor view, you can specify to use Disk Monitors tomonitor the space usage of available entries. To specify Disk Monitors, select thefollowing items from the Available table in the window: managed system >Director Agent > Disk Monitors. When specifying Disk Monitors for a managedsystem that is running the AIX, UNIX or Linux operating system, some foldersunder the root path (including /lib, /home, /opt, and others) are not visible. Youcan use Disk Monitors to monitor space usage information for only those entriesshown in the Available table.

Explanation

Disk Monitors supports monitoring hard disk drives but does not supportmonitoring file systems. Disk Monitors displays only those file systems under theroot path that are hard disk drives.

Resolution

Use Disk Monitors only when you want to monitor space usage information forhard disk drives.

198 IBM Systems Director Troubleshooting and Support Guide

Error is encountered while loading shared librariesThis problem affects the Process Management task. It occurs on only thosemanaged resources that run Linux.

Problem

When running the Process Management task or any action that uses Linuxoperating-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 variableLD_ASSUME_KERNEL, which is incompatible with commands launched from theJava environment. This problem affects several commands, including the followingcommands:v psv topv pgrepv pstree

Resolution

Set the LD_ASSUME_KERNEL variable to an empty value as part of the action. Forexample, when running ps as a Process Management action, instead of issuing thecommand ps -ef, use LD_ASSUME_KERNEL=;ps -ef.

Power Systems server IVM events appear in the event log withincomplete Event Text and Source fields

(IBM Systems Director 6.1 only) This problem affects Power Systems. This problemis 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 theactual event type in the Component Type field and the actual source of the eventin the Source field.

Events are not created immediately when a threshold isexceeded

This problem affects monitoring and thresholds on any resource.

Problem

When the value of a monitor goes above the threshold level that you specified, anevent is not immediately created.

Troubleshooting and support 199

Explanation

By default, an event is generated only after the value of the monitor is above thethreshold for five minutes.

Resolution

Change the minimum duration for the threshold to the desired value.

Incorrect events reported for NICs that have a teamingconfiguration 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 asactive-standby. The problem is limited to NICs installed in managed systems thatare running any supported Windows operating system.

Problem

When a network interface card (NIC) in a managed system has a teamingconfiguration of active-standby, IBM Systems Director incorrectly reports someevents for that NIC.

Note: Usually, an NIC is configured as active-standby only when the managedresource contains more than one active NIC.

Explanation

Currently NIC teaming supports only an active-active configuration. Because NICteaming does not support an active-standby configuration, associated events arelimited to SwitchOver and SwitchBack. Look for NIC teaming events in theSystems Director Event Log for the managed server (out-of-band) and in theService Processor Console web user interface.

Table 9. Expected and reported events for NIC with teaming set to active-standby

NIC teaming Symptom Expected event1Reportedevent2

Primary = FailedSecondary = Active

Primary NIC fails; teamingswitches from primaryNIC to secondary NIC

SwitchOver SwitchOver

Primary = ActiveSecondary = Standby

Primary NIC comesonline, teaming switchesfrom secondary NIC toprimary NIC

SwitchBack SwitchBack

Primary = ActiveSecondary = Failed

Standby NIC fails Offline SwitchOver

Primary = ActiveSecondary = Standby

Standby NIC comes online Online SwitchBack

1: A network interface card with a teaming configuration of active-active correctly reportsthe expected NIC events.

2: In a Broadcom “Active-Standby” NIC teaming environment with “Auto-Fallback” modedisabled, Systems Director will not report these events. Instead, either Offline or Onlineevents will be reported according to the Primary or Secondary NIC status.

200 IBM Systems Director Troubleshooting and Support Guide

Resolution

The problem identified in this topic is a known limitation for NICs with a teamingconfiguration of active-standby.

Monitored memory values are too highThis problem affects IBM Systems Director for 6.1.0 and earlier when monitoringmemory on AIX and Linux on Power Systems.

Problem

When using IBM Systems Director for 6.1.0 and earlier, the monitoring values formemory, 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 valuein MB instead of bytes. Upgrading to IBM Systems Director 6.1.1 or later resolvesthis problem.

Monitored disk space values are too low(IBM Systems Director 6.1 only) This problem affects monitoring of disk space onAIX. 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 menuThis problem affects monitoring on any resource.

Problem

When you select a resource on the Resource Explorer page and click Actions, themonitoring tasks are not listed.

Explanation

Monitoring actions are available for only those resources that are running PlatformAgent or Common Agent and that are, at a minimum, online and accessible. Thereare also other monitoring restrictions that might apply based on the resource type

Troubleshooting and support 201

or relationships. If a system cannot be monitored for any reason, the monitoringoptions will not appear in the Actions menu.

Resolution

Ensure that the resource is online and accessible. If you still cannot accessmonitoring actions for the selected resource, other restrictions exist and you willneed to investigate them individually.

Monitors are not listed for the selected resourceThis problem affects monitoring on any resource.

Problem

When you click Show Monitors on the Monitors page, the Monitor View pagedisplays the statement No Data Available and no monitors are listed.

Explanation

There are many possible explanations for this specific problem, three of which aremost 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 restrictionsthat might apply based on the resource type or relationships. If a system cannotbe 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 forvarious 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 canbe monitored, implement the following potential solutions to cover both possibleexplanations 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 monitoringsolutions works, use another method to collect the data.

No data available error for AIX and VIOS monitorsThis problem affects AIX monitors and VIOS monitors when inspecting AIXmanaged systems or VIOS managed systems.

Problem

Using an AIX monitor or VIOS monitor in IBM Systems Director Server to inspectan AIX managed or VIOS managed system causes “No Data Available” to displayin all monitor entries.

202 IBM Systems Director Troubleshooting and Support Guide

Explanation

The AIX monitor and VIOS monitor tasks in IBM Systems Director require that theAIX managed systems and VIOS managed systems be running specific versions ofthe operating system or common agent.

Resolution

To resolve the problem with the AIX monitor, make sure that you have one of thefollowing installed on the AIX managed system:v AIX 53 TL10 or earlier, with Common Agent 6.1.2 reinstalledv AIX 53 TL11 or laterv AIX 61 TL03 or earlier, with Common Agent 6.1.2 reinstalledv AIX 61 TL04 or later

To resolve the problem with the VIOS monitor, make sure that you have one of thefollowing 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 reinstalledv VIOS 2.1.2 or later

Predictive Failure Analysis events not reported for Systemx3755 M3 servers

The problem affects the reporting of Predictive Failure Analysis events frommanaged IBM System x3755 M3 servers.

Problem

Platform Agent fails to report Predictive Failure Analysis events for processors orDIMMs that occur on x3755 M3 servers. Because the specified events are notreported, you cannot see any of those events in the event log for the operatingsystem 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 DIMMsv IBM IPMI firmware commands do not work on x3755 M3 servers

Platform Agent cannot report the specified events unless detection of and supportfor Predictive Failure Analysis sensors and support for Predictive Failure Analysissensor events is added to the non-IBM BMCs.

Resolution

The failure to report Predictive Failure Analysis events is a known limitation that isspecific only to System x3755 M3 servers. You can view Predictive Failure Analysisevents in the IBM Systems Director event log for the managed x3755 server(out-of-band). Additionally, you can use the service processor console web interfaceto view the events.

Troubleshooting and support 203

Resource is not returned by the browse functionThis problem affects monitoring on any resource.

Problem

The resource that you want to monitor is not displayed in the context chooserwhen you click Browse on the Monitors page.

Explanation

Monitoring actions are available for only those resources that are running PlatformAgent or Common Agent and that are, at a minimum, online and accessible. Thereare also other monitoring restrictions that might apply based on the resource typeor relationships. If a system cannot be monitored for any reason, it will not showup in the list of monitors when you browse and the monitoring options will notappear in the Actions menu.

Note: If nothing happens when you click Browse, there are no resources thatmatch the criteria for monitoring.

Resolution

Ensure that the resource is online and accessible. If the resource is still notdisplayed when you click Browse, other restrictions exist and you will need toinvestigate them individually.

Resources are encountering problems that you need tomonitor and manage

This problem can affect any resource.

Problem

You encounter problems with your resources and aren't sure how to gatherinformation about, monitor, or manage the problems.

Explanation

Any resource can encounter problems. IBM Systems Director provides a set of toolsthat you can use to monitor and manage the status and health of resources in yourenvironment from a single interface. Use these tools to monitor and manageproblems 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 nochanges

This problem affects Microsoft Internet Explorer and Mozilla Firefox browserswhen running IBM Systems Director 6.1.2 and earlier.

204 IBM Systems Director Troubleshooting and Support Guide

Problem

When you try to close the process management launched task, even if you havenot made any changes, you are prompted to save your changes before the windowcloses.

Resolution

Electing to save or not save yields the same result, so just pick one and click theappropriate button to close the confirmation window and the launched taskwindow.

Two microprocessor monitor resources are displayed whenonly one microprocessor exists

This problem affects the Resource Monitor task on managed resources runningWindows with Hyper-Threading capability.

Problem

When you view the microprocessor monitor resources after you run the ResourceMonitors task on managed resources running Windows with Hyper-Threadingcapability, resource attributes for two microprocessors are displayed despite thefact that the resource contains only one microprocessor.

Explanation

This problem occurs when Hyper-Threading is enabled for the microprocessor. IfHyper-Threading is enabled, the Resource Monitors task displays twomicroprocessor monitor resources when only one microprocessor exists. TheResource Monitor task draws data from the operating system, and the operatingsystem interprets a single Hyper-Threaded microprocessor as two logicalmicroprocessors.

Update manager troubleshootingThis section provides information about problems and workarounds related to theupdate manager plug-in.

Unable to import updates from network mounted directoriesUpdate Manager is unable to import updates from network mounted directories inWindows.

Problem

When using the importupd command or Import Updates task, if the path given isfor a network mounted directory, the message “The specified file {path} was notfound.” is displayed and no updates are imported.

Explanation

The IBM Director Server service runs as a local Windows service, which does nothave access to network shares mounted in user space. All IBM Systems Directorcommand-line interface (smcli) commands are actually performed by the runningserver and not by smcli.

Troubleshooting and support 205

Resolution

Copy the updates to a local drive and import the updates from there.

Getting Started wizard for update manager indicates thatsome systems are not supported

After selecting systems in the Getting Started wizard, a message is displayedindicating 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 theselected 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 collectedfor it. Some delay can occur between inventory being collected and processed, sowait some time before trying the Getting Started wizard again.

Explanation

Updates are supported only for certain operating systems and IBM hardwareplatforms. The affected systems might not be one of these supported platforms.

When there is no update support currently available for any aspect of a givensystem, the Getting Started wizard indicates that IBM Systems Director does notsupport 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.

Problem

When using the Getting Started, Install staging, and Install wizards, the Systemspage does not allow selection and addition of a particular system.

Resolution

Ensure that the system is accessible, software inventory has been collected for it,and the desired updates apply to the system.

206 IBM Systems Director Troubleshooting and Support Guide

Error occurred trying to start the TFTP server used for IBMBladeCenter and System x updates

This problem occurs when trying to start the TFTP server used to obtain updatesfor IBM BladeCenter and System x systems.

Problem

Update manager for IBM BladeCenter and System x provides a TFTP serverembedded within the management server to aid in the distribution of update filesto certain IBM BladeCenter devices. This TFTP server is started when the userselects Use the management server as a TFTP server in the BladeCenter Settingstab. You might receive error message DNZUPX056E: An error occurred trying tostart the TFTP server on the management server.

Explanation

There are several reasons for an error when starting the TFTP server. The mostcommon cause is that the port used by the TFTP server is already in use byanother 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, shutdown that application and try to restart the TFTP server by selecting the Use themanagement server as a TFTP server option on the BladeCenter Settings page.

Alternatively, an external TFTP server can be used by specifying the Use Systemoption, and specifying the TFTP root directory and Relative path to updates fields.

Additional information

Most platforms provide a command, such as netstat on Windows and Linux, tocheck the availability of the ports.

Compliance is not accurate for a systemUpdate 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 beout of compliance, or a system is shown as being out of compliance after an installhas been performed that should have brought it into compliance.

Investigation

Ensure that the system is unlocked and the latest software inventory has beencollected. After collection, the inventory data can take some time to be fullyprocessed, at which point the compliance information should be accurate.Processing of inventory occurs at a default time interval of ten minutes, so youshould 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.

Troubleshooting and support 207

v If a static update group is being used, only updates that are applicable to thesystem will cause an out-of-compliance indication.

In either of these cases, the inventory data must be current and processed in orderfor accurate results to be displayed.

Resolution

Unlock the system and ensure that the latest inventory has been collected.

Unable to find update compliance task logsThe log files produced by the update compliance policies for a given system arenot found with the log files for tasks run on that system.

The update compliance task cannot be found on the Task Management > Activeand Scheduled Jobs page.

Explanation

The update compliance task is run automatically when changes happen such as theimport or acquisition of new updates, the completion of inventory collection on asystem, or changes to the membership of a group in a compliance policy. Since thetask is run automatically by update manager as opposed to being scheduled by auser, it does not appear in the Active and Scheduled Jobs page.

Resolution

The compliance task information, including it's logs, can be viewed from thesystem that compliance was run against, by following these steps:1. Click Resource Explorer > 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/Omodules

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.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.

208 IBM Systems Director Troubleshooting and Support Guide

Update compliance is not refreshed when adding a nestedgroup to a compliance policy

Nested update groups and system groups for update manager do not inheritcompliance policies.

Problem

A compliance policy is defined for a static System group or Update group. Anothergroup 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, nestedgroup.

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 theyare included in.

For example, if a compliance policy is made up of a static Update group thatcontains updates and other Update groups, only the updates of the group in thepolicy will be validated for compliance to the systems in the same policy. Anythingwithin the nested Update group will not be considered for validation of thecompliance policy.

Resolution

Create a separate compliance policy for nested System groups and Update groups.

Compliance issues not resolved after successful install ofupdates

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 againstthe out-of-compliance systems on which the updates were installed. If theinventory collection completed successfully, check to see if the compliance jobfailed. 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.

You can also look for a failed Update Compliance job activation in theout-of-compliance system's property page. Follow these steps:1. In the IBM Systems Director Web interface navigation area, click Resource

Explorer.

Troubleshooting and support 209

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.

Resolution

Collect inventory against the out-of-compliance system to activate compliance.When the Update Compliance job completes successfully, the compliance issuesshould be resolved.

Update compliance issue remains unresolved after installingIBM Director Agent 5.20.x updates on Linux systems

In inventory, the version property of the IBM Director Agent 5.20.x does not getrefreshed properly after an update, which means that the compliance issue remainsunresolved.

Problem

After installing an IBM Director Agent 5.20.x update on a Linux system, theversion property does not get updated properly. The update installation completessuccessfully, but the version information does not get updated correctly, whichcauses the update manager compliance policy to report that the update still needsto be applied.

Resolution

To resolve this issue:1. Restart IBM Director Agent 5.20.x 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.

Running out disk space during update download can causerandom application errors and server startup errors

This problem can occur when downloading updates that consume a large amountof disk space.

Problem

Updates may consume a large amount of space in the file system, typically /opt orc:/, where IBM Systems Director is installed. Some updates, such as HardwareManagement Console and AIX, can consume gigabytes of disk space when they aredownloaded or installed. Running out of free space can cause random applicationfailures and problems starting the IBM Systems Director Server. This considerationis especially important for AIX systems.

210 IBM Systems Director Troubleshooting and Support Guide

Resolution

Ensure that adequate free space exists in the file system where the updates arebeing downloaded. The amount of free disk space must be greater than theMaximum disk space to use value in the update Settings function. The maximumdisk space to use value can be checked by clicking Release Management >Updates > Settings, and then checking the value on the Locations tab.

Additional information

The default maximum disk space to use for updates is 10 gigabytes. Ensure thatthis amount of disk space or more is free on the file system where IBM SystemsDirector is installed.

Download of updates fails due to proxy server connectionissues

Test connection, check for update, or download tasks fail on systems connected tothe Internet through a proxy server.

Problem

When you try to test the connection to the Fix Service Provider, or check forupdates, or download updates and the task fails because the function cannotconnect to the Internet using the proxy server (this only applies to client systemsthat 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 toconnect to IBM and download updates. Ensure that all of the followingprerequisites 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 theInternet through ports 80 (HTTP) and 443 (HTTPS). The firewall and proxyserver 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 proxyserver to use Digest or NTLM authentication, you will be unable to connect toIBM.

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.

Additional information

The IP addresses and ports used to contact the Fix Service Provider are defined infiles that reside in this directory:

Troubleshooting and support 211

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 toattempt to download a recent version of theserviceProviderIBMLocationDefinition.xml file.

Download of updates fails with an error of download sizeexceeded

This problem occurs when the Maximum disk space to use setting is set to anamount 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 taskhistory log contains message 'ATKUPD812E Cannot download updates because theupdates 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 anamount that is smaller than the size of the updates you want to download. Tocorrect 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 inMegabytes (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 issmaller.

Install and Installation staging tasks not available for anupdate

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 eithernot available or not selectable for a particular update.

Resolution

This will happen when the update is not known to be appropriate for anydiscovered system. If you know that the update should be appropriate for adiscovered system, ensure that the system's software inventory has been collectedand is current.

212 IBM Systems Director Troubleshooting and Support Guide

Once inventory is collected, the processing of the inventory can still take severalminutes. The menu actions will not be available until after the inventory has beenprocessed.

IBM BladeCenter Install and Installation Staging tasks failwhen using an FTP or TFTP server

This problem occurs when using the FTP or TFTP server for the install orinstallation staging tasks for IBM System x and IBM BladeCenter systems.

Problem

Errors occur when attempting to perform installation staging tasks using FTP orTFTP servers. Installation staging is the task that copies installable firmware files tothe FTP or TFTP server. The installation staging task can be explicitly requested, orit 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 IBM BladeCenter Settings tab (Release Management > Updates

> Settings > BladeCenter) is configured with the correct settings to access anduse the FTP or TFTP server.Check that the following settings are correct:– 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 orTFTP). Ensure that the correct protocol is configured. Note that if the updatedescriptor indicates that both FTP and TFTP are supported, and if both FTP andTFTP servers are configured on the IBM BladeCenter Settings page, the TFTPserver will be used.

v Ensure that the system selected to be used as the FTP or TFTP server has beenunlocked 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 devicesusing SNMP fails

This problem can occur when using SNMP for the installation of IBM BladeCenterupdates.

Problem

Installation failures occur when attempting to install updates for IBM BladeCenterdevices (such as IBM BladeCenter Management Modules, Advanced Management

Troubleshooting and support 213

Modules, and Pass Thru Modules) using SNMP.

Resolution

For installation staging task failures, see “IBM BladeCenter Install and InstallationStaging 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 obtainedfrom a TFTP server. There is one management server IP address that is chosenrandomly from the list of IBM Systems Director Server IP addresses. If themanagement server acts as the internal TFTP server, this IP address is kept asthe TFTP IP address. However, since TFTP settings and TFTP IP addresses arekept in persistent storage, these two IP addresses might be different in somecases. For example, IBM Systems Director Server has two IP addresses, IP-A andIP-B, and IP-A is the initial management IP address and TFTP IP address. AfterIBM Systems Director Server is restarted, IP-B is chosen as the management IPaddress. At this time, the TFTP IP address remains unchanged, as IP-A, becausethe TFTP setting is stored in persistent storage. So, if you want to use themanagement server as a TFTP server, keeping the TFTP IP address andmanagement server IP address the same, you need to first disable TFTP andthen enable TFTP again.

v If using an external TFTP server, ensure that it is unlocked (access granted) andonline.

v When using a different TFTP server than the one included with the managementserver, make sure you correctly set the TFTP root directory. If that value is notset appropriately, the updates will not be accessible by the Management Moduleusing TFTP, which will cause the installation process to fail. The TFTP rootdirectory must already exist on the TFTP server.

v When using a different TFTP server than the one included with the managementserver, make sure the Relative path to updates value is not too long. A longpath name can cause the installation process to fail. A path name shorter than 25characters in length is recommended.

v To help ensure successful installations, consider the points in “Updateconsiderations for IBM BladeCenter I/O Modules and Management Modules”.

Installing out-of-band updates for IBM BladeCenter devicesusing Telnet fails

This problem can occur when using Telnet for the installation of IBM BladeCenterupdates

Problem

Installation failures occur when attempting to install updates for IBM BladeCenterdevices (such as switch and bridge modules) using Telnet.

214 IBM Systems Director Troubleshooting and Support Guide

Resolution

For installation staging task failures, see “IBM BladeCenter Install and InstallationStaging 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 IBM BladeCenter Settings tab (ReleaseManagement > Updates > Settings > BladeCenter). Some switches use FTPonly; some use TFTP only; some can use either FTP or TFTP. If the updatedescriptor specifies that both FTP and TFTP are supported, and both FTP andTFTP servers are configured on the BladeCenter Settings tab, then TFTP will beused.

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 TFTProot directory. If that value is not set appropriately, the updates will not beaccessible by the target switch module using FTP or TFTP, which will cause theinstallation process to fail. The directory must already exist on the FTP or TFTPserver.

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 SystemsDirector 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 conformto the requirements of the FTP server.

Installing an update takes too much timeThe 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 isalways performed. Steps 1 and 2 are done as part of the installation process, if it isdetermined 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 themost time to complete. The size of the update will greatly impact the performanceof the first two steps.

Troubleshooting and support 215

Before installing the update, the download task can be selected to download theupdate. Once this task completes, the installation staging task can then be ran onthe update to stage it over the customer network for eventual installation.

If manually running the download and install staging tasks does not improve thetime that it takes to run the install task, compare the performance of installing withIBM 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 forerrors.

Remember that some updates take a considerable amount of time to install due tothe nature of the platform, operating system, or the update itself.

Resolution

Run the installation staging task before the install maintenance window, to avoidthe time it takes to download and transfer the update over the network. The installtask should then provide better performance during the installation maintenancewindow.

Install fails when using system groups or update groupsPerforming an install or uninstall fails when using one or more system groups orupdate groups.

Problem

The Install or Uninstall task using system groups or update groups does notsucceed due to missing update requirements or dependencies.

Explanation

The Install wizard and Uninstall wizards do not resolve group membership untiltheir tasks runs. Group membership is not resolved at the time that the wizard isrun. This means that the task may fail because information about updates, such as:update requirements, manual downloads, manual installation, and system restartscannot 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 installedindividually instead of selecting the update group. This will cause the wizard toobtain the necessary information about update requirements.

Updates from an update group have not been installedWhen 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. Whenthe task completes, you find that some of the updates that were in the group whenthe task was scheduled, have not been installed.

216 IBM Systems Director Troubleshooting and Support Guide

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 thetask 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 theupdate task is scheduled. It is resolved when the task runs.

v The update group contained updates that require a manual download. A manualdownload cannot be automatically performed, so that task fails. Since themembership of the update group was not determined when the update task wasscheduled, the user could not be alerted to this possibility.

v The update group contained updates that had special install instructions. Similarto the previous scenario, this cannot be done automatically, and the user cannotbe 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 thathave failed, instead of using an update group. The wizard can detect manualdownloads and special installation instructions when it is given only one update toinstall.

Path length is limited to 64 characters when updating IBMBladeCenter Out of Band components

This limitation affects update manager when applied to out-of-band IBMBladeCenter components, such as Management Modules, Advanced ManagementModules, and Pass-through Modules.

Problem

The install task for an out-of-band IBM BladeCenter update will fail when the pathof 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.

Resolution

Ensure that path of the TFTP staging server is fewer than 64 characters in length.

Additional information

If you are updating IBM BladeCenter Management Modules with version BRET86Cor earlier, the path length is limited to 32 characters.

Staging of updates to TFTP server can fail on extremely slownetworks

This limitation affects update manager when staging updates to a TFTP server.

Troubleshooting and support 217

Problem

On extremely slow networks, staging of updates to TFTP server may exceed aninternal timeout value, causing the install task to report a failure, even though thefile 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 TFTPstaging server. Select one whose network connection speed is faster.

Updating IBM Director Agent version 5.20.1 on operatingsystems other than Windows fails

Updating IBM Director Agent version 5.20.1 on operating systems other thanWindows fails

Problem

When using an operating system other than Windows, updating IBM DirectorAgent version 5.20.1 fails.

The status of the install request will be "Complete with errors". The task log willcontain entries similar to this sequence of errors###########################################################################ATKUPD702I Update Installation service: A new request is active.ATKUPD740I Update Installation service: Provider "Legacy Agent InstallExtension" 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.

The presence of errors DNZSWD204W and DNZSWD205I is most significant.

Resolution

You must manually update IBM Director Agent version 5.20.1 on operatingsystems other than Windows.

Additional information

To update IBM Director Agent version 5.20.1 manually, complete the followingsteps: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.

218 IBM Systems Director Troubleshooting and Support Guide

AIX upgrades that skip a Technology Level may not reportcorrect 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 aTL, 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 AIX5300-06-08-0831 to AIX 5300-08-03-0831 is an upgrade from AIX 5.3 TL6 SP8 to AIX5.3 TL8 SP3, skipping AIX 5.3 TL7.

Explanation

New AIX base level file sets may be introduced in a Technology Level. Forexample, when upgrading from AIX TL6 to AIX TL8, there might be new baselevel file sets that were introduced in AIX TL7. Updates to these base level file sets(for example, updates that must be installed in order for a system to report that itis at AIX TL8) might not have been selected for installation, because an upgradeoperation can only select updates for previously installed file sets (for example,those previously installed on AIX TL6). After the upgrade is completed this resultsin 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 itis at the expected Technology Level, the installation should be performed again.This could result in the installation of the missing file sets that are necessary forthe AIX system to report the correct operating system level.

If no change occurs after performing the installation again, contact your serviceprovider to determine the missing file sets that must be installed in order for theAIX system to report the expected level.

Best practices for working with updates for IBM iThis problem affects users who are installing updates to IBM i.

Problem

Update groups for IBM i agents can contain a large number of updates, whichmight cause performance, memory and file space issues on the IBM SystemsDirector Server.

Actions1. Use a 64–bit 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 someconfigurations, two input/output adapters have to be physically paired. Referto the IBM i documentation for more information.

3. For tasks that contain a large number of updates, such as IBM i PTF groups, itis recommended you use a high performance database, such as IBM DB2.

4. When working with IBM i updates, it is recommended that you work withone update group at a time. For example, when checking for IBM i 5.4updates, first check for Hiper PTFs and let that check complete before

Troubleshooting and support 219

checking for additional updates. Performing three individual checks willprovide better results then attempting a single check for Hiper, IBM DB2 andJava, for example. In addition, to optimize checks, you can schedule yourupdate task checks. Finally, it is a good practice to run tasks that check forand install updates during non-peak hours.

5. Avoid selecting updates that are not necessary for your system. Storingunnecessary updates on the IBM Systems Director Server affects performance.

6. To reduce the time needed to install IBM i updates, the updates that areneeded for install can be downloaded from the fix service provider to the IBMSystems Director Server, before the install task is started. When the updatesare already on the server, the install only needs to send the updates from theIBM Systems Director Server to the IBM i system. The install task can bescheduled 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 beimproved by increasing the amount of memory available to Java. To increasethe memory, edit <Director install directory> /lwi/conf/overrides/director.javaopt. On 32–bit systems that have IBM Systems Director Serverinstalled, change the value for -Xmx to 1792m. For example, -Xmx1792m.

Important: Before increasing the memory available to Java, make sure there isenough 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 iupdates. It might be necessary to increase the size of the /opt filesystem.

9. To allow more time for collecting inventory on an IBM i system, the defaultdiscovery timeout value on the IBM Systems Director Server can be increasedby editing a properties file that is read when the IBM Systems Director Serveris started. The timeout value is set by adding or changing the followingproperty 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 suggestedvalue is 75 minutes.

10. When running a check for an updates or collect inventory task, another job issubmitted in the background after the task completes. It is important to allowsufficient time for the background job to complete before starting an installupdates task. This background job, named Update Compliance, can bemonitored from the Applied Activities tab on the System Properties page.

11. The performance of the IBM Systems Director Server can be increased byremoving updates that are not needed. For example, if IBM WebSphere®

Application Server group PTFs have been downloaded but are no longerapplicable to the systems because the product has been removed, then thoseupdates can be removed from the IBM Systems Director Server. To removeupdates from the server, use this command:smcli cleanupd -am

Uninstall fails because a restart of an IBM i system is requiredThis problem affects IBM i (formerly i5/OS®) systems.

220 IBM Systems Director Troubleshooting and Support Guide

Problem

When you try to uninstall updates to IBM i systems using update manager, thetask 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 completethe uninstall' is in the log file. IBM i systems are not restarted automatically byupdate manager.

Resolution

Perform the restart.

Show installed updates and Show and install updates tasksdo not display all updates

The show updates views do not display all updates. Some updates are missing.

Problem

When using Show installed updates, Show and install updates, viewing updategroups, or other places where updates are listed, not all updates are displayed.

Investigation

Ensure that the system is unlocked and the collected software inventory iscomplete and current. Once inventory completes, it needs to be processed, whichcan take several minutes. When complete, the update information on what isneeded or current should be accurate.

Explanation

Update manager will include in these views only the updates that update managersupports. Therefore, Show installed updates should not be considered a completeview of all updates installed on a system, but only a view of the updatessupported for management by update manager. This rule applies to all views.

Likewise, updates that cannot be managed due to inadequate information mightnot be displayed. If an update is installed but information on that update has yetto be acquired by a Check for updates, the update will not be visible formanagement.

Updates that are part of a collection, such as a service pack or larger updatepackage, will not be individually displayed unless the Related resources action ischosen on the parent update collection.

Resolution

If an update is supported by update manager and is not being displayed, ensurethat information on the update has been downloaded by running the Check forupdates task. Also, ensure that the collected software inventory for the system iscurrent and complete.

Troubleshooting and support 221

Commands troubleshootingThis section provides information about problems and workarounds forcommand-line interface included in IBM Systems Director, including smcli, mpcliand soapcli.

Help and error messages for the smcli command display onlyin English

This problem exists in the IBM Systems Director Server when using the commandline interface.

Problem

When using the command line interface on management servers running AIX andLinux, help and error messages for smcli command itself (not all IBM SystemsDirector 6.1 commands) does not display in Italian (it), Brazilian Portuguese(pt_BR), Chinese and Japanese locales. They display only in English.

Resolution

To resolve this issue, run the following command:chmod +x /opt/ibm/director/bin/msgpool

Unable to display man pages on SUSE Linux EnterpriseServer 9.x

This problem affects only management servers running SUSE Linux EnterpriseServer 9.x.

Problem

The Linux man pages are encoded in UTF-8. The man command in SUSE LinuxEnterprise Server 9.x is not able to process UTF-8, and therefore cannot display theman pages.

Resolution

To get help for the smcli commands on SUSE Linux Enterprise Server 9.x, performone 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, adescription 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 defaultwhen the primary language has been set to Japanese.

Unable to run a specific smcli commandThis problem affects management servers only.

222 IBM Systems Director Troubleshooting and Support Guide

Investigationv 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 apermission category assigned to each permission.

v Management servers running a new installation of Windows requires a Cruntime DLL, mscvr80.dll, from Microsoft to run smcli commands. If this DLLis missing, you will see the following error when you attempt to run an smclicommand:The system cannot run the specified program.

You can obtain the DLL by downloading and installing vcredist_x86.exe fromMicrosoft at https://www.microsoft.com/downloads.

v Verify that the management server satisfies the hardware and softwarerequirements. For more information about hardware and software requirementsfor IBM Systems Director Server, see the IBM Systems information center atpublib.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.x on a machine on which IBM Director5.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\CurrentVersionregistry key:Root =install_root\IBM\Director\

Data=install_root\IBM\Director\data\

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

– (Linux and AIX only) Edit the etc/ibm/director/twgserver/twgserver file andchange following key-value pair:TWG_ROOTDIR =/opt/ibm/Director

toUSMI_ROOTDIR =/opt/ibm/Director

Unable to run smcli commands from a directory other thaninstall_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 commandThis problem affects management servers only.

Troubleshooting and support 223

Problem

Most dircli commands are supported in this release for compatibility with IBMDirector version 5.20.

Investigationv Verify that the dircli command that you want to use is supported in this release.

Only dircli commands that manage managed-objects, groups, discovery andinventory, events, tasks and jobs, SNMP devices, and virtualization aresupported.

v Verify that the CLILEGACY environment variable is set it to a value of 1. Manysmcli and dircli commands have the same name. By setting CLILEGACY to 1,you can run the commands using the dircli syntax and output format.

Unable to change the language (locale)This problem can affect management servers running any supported operatingsystem.

Investigationv You can specify the language through the operating system language settings.

Note: The -L | --lang option and the DIR_LANG environment variable are nolonger available. Use of the -L | --lang option will result in a usage error. If theDIR_LANG environment variable is set, it will be ignored.

Unable to use double-byte character set languages in AIXThis 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 serverrunning AIX.

Investigation1. If you are running commands from a remote system, verify that the remote

system supports the desired double-byte character set by entering thiscommand 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=languageexport 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 isthe 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.

224 IBM Systems Director Troubleshooting and Support Guide

gb18tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-gb2312.1980-0rom9tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-iso8859-1

Resolution1. 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 JAVA_HOME/lib

directory from a command line and enter these commands:mv font.properties.zh font.properties.zh.origcp font.properties.zh.4.3.3 font.properties.zh

Additional information

You can find more information about problems using double-byte character setlanguages on the Web at:www.ibm.com/developerworks/java/jdk/aix/118/README.html

Output is empty for system and inventory commandsThis problem affects management servers only.

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 discoversystems using the discover command. If no systems have been discovered, theoutput of the lssys command will be empty.

Before you can run the lsinv command, you must first collect inventory for thetargeted systems by running collectinv command. If no inventory has beencollected, the output of the lsinv command will be empty.

Resolution

Run the discover command to discover all manageable systems, and run collectinvto collect inventory for the targeted systems.

Unable to connect to the CLI daemonThis problem affects management servers only.

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 namedCLISocketKey.dat at root\data folder. This file is required for smcli to communicatewith IBM Systems Director Server. The error is displayed when IBM SystemsDirector Server started and the CLISocketKey.dat has not yet been created.

Troubleshooting and support 225

Resolution

Wait a few minutes, then run the command again.

Storage commands troubleshootingThis section provides information for specific problems and workaroundsassociated 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 collectedinventory data to perform their function and therefore is required for successfuloperation.

v Some command problems actually might be problems with IBM SystemsDirector components. Review all troubleshooting topics for possible solutions.

Strategies for solving problems with storage commandsThis 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 onthe system that you are using, you might be required to enter the path using theforward slash (/).

You also can view the audit log file in IBM Systems Director Web interface. ClickOptions > Auditing Administration. In the Auditing Administration window, clickView 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 Serverv Viewing the storage audit log filev Activating a taskv 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 forthe targeted hostThis problem affects storage commands that target host systems.

Problem

When running any smcli storage command (such as lsnshost and mknspath), thefollowing error is displayed:Could not find any Fibre Channel ports, SAS ports, or ISCSI name for the host

226 IBM Systems Director Troubleshooting and Support Guide

Explanation

Before you can run any storage command, you must first collect inventory for thetargeted host systems by running collectinv command. During inventorycollection, data such as Fibre Channel and SAS port information is collected.

Tip: Ensure the targeted host system is unlocked before collecting inventory.

Resolutionv 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 beaccessible for this command to work.

lsnssys command does not display storage systems in outputThis problem affects the lsnssys command that targets storage systems.

Problem

When running the lsnssys command, the output does not list the storage systemsthat has been previously discovered. If the storage system is not shown in theoutput, then no storage provisioning can be performed on the targeted storagesystem.

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 thestorage system is set to a valid value.

lsnssys lists storage systems as inaccessibleThis problem affects the lsnssys command that targets storage systems.

Problem

When running the lsnssys command, the output shows the systemAccessibleproperty as false for the targeted storage system.

Investigationv 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 IPaddress of the controllers.

v Verify that any SMI-S or CIM provider is running on the storage system toensure that the IBM Systems Director Server can manage the storage system.

chnsvol command is not supportedThis problem affects the chnsvol command that targets storage systems.

Troubleshooting and support 227

Problem

Some storage systems support renaming existing volumes, and some do not. Forexample, DS3000, DS4000, DS6000™ support renaming volumes. IBM BladeCenterSAS RAID Controller Module does not support renaming volumes. When a storagesystem 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 displayedThis problem affects storage commands that target host systems.

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.ProviderExceptionDescription: Delete Protocol Controller invalid parameter)

Resolutionv 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, stopusing the SANtricity software. If you used proprietary mechanisms, you mustclean up the references.

Host type matching the requirements is not supported bystorage systemThis problem affects storage commands that target host systems.

Problem

When running the chnssys command, you receive the following error:Exception: Host type matching the requirements is not supported bystorage system system

where system is the storage system you specified in the chnssys command.

Explanation

Resolutionv 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. Tocheck the supported values and also to list the supported values for all thestorage systems in your configuration, run the lsnssys command.

228 IBM Systems Director Troubleshooting and Support Guide

v Ensure that you are running this common on a supported storage system. Thechnssys command is on valid only for the DS4000 family of storage systems. Itis not supported for DS3000, DS6000 and Serial Attached SCSI (SAS) RAIDController Modules.

Session limit out of resource errorshis problem affects storage commands that target host systems.

Explanation

If administrative security is not enabled for a managed Qlogic switch, issuing aseries of storage commands might cause session limit out of resource errors. Thismight to occur if more than 15 storage commands are issued in a five-minuteperiod. The problem occurs because with security disabled, session handles are notcleaned up until they time out after five minutes.

Resolution

To resolve this problem, enable the administrative security for the switch. See theswitch documentation for information about performing this configuration.

Zone and zone set are present when zoning is disabledThis problem affects storage commands that target host systems.

Problem

A zone and zone set are still present even when zoning is disabled. This situationis evident when running the lsnshost command.

Resolution

Detaching the last zone in a zone set using the chnshost -D command might notremove the zone.

You must manually clean up the zone and zone set by logging into the affectedswitch. See the switch documentation for information on performing a manualclean up.

Update commands troubleshootingThis section provides information for specific problems and workaroundsassociated with the update commands.

Tip: Some command problems actually might be problems with IBM SystemsDirector components. Review all troubleshooting topics for possible solutions. Foradditional troubleshooting information, see the IBM Systems Director ReleaseNotes.

The importupd command fails with error message 'The specifiedfile 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.

Troubleshooting and support 229

Investigation

Ensure that all path names that contain spaces are enclosed in quotes. Determine ifthe specified file path exists.

Resolution

Place quotes around the file path name, if it contains spaces. Ensure that thespecified file path does exist.

The cleanupd command does not remove updatesWhen trying to remove an update using the cleanupd command, the update is notremoved.

Problem

Trying to remove a single update using the cleanupd command with the -m and -uoptions does not remove the update.

Investigation

Run the lsupd command with the -a and -l options to see if the update issuperseded by any other updates.

Run the lsupd command with the -m option to see if the update is a collection thatcontains other updates.

Explanation

The update may be involved in a supersedes, requires, or federates relationshipwith another update and cannot be removed without using the cleanupdcommand with the -F (--force) option.

Resolution

Run the cleanupd command with the -F (--force) option.

Console logging and tracingYou can view and modify the configuration properties of the diagnostic traceservice. This information pertains to logs and traces for the IBM Systems DirectorWeb interface framework only; it does not pertain to your managed resources. If aproblem occurs with the Web interface framework and you must contact your nextlevel of support, your service provider, or an IBM Systems Director servicerepresentative, your service representative might ask you to adjust theseconfiguration properties.

To change the settings for console logging and tracing, in the IBM Systems Directornavigation area, expand Settings and click Console logging and tracing.

230 IBM Systems Director Troubleshooting and Support Guide

Sensor logs and debuggingIBM Systems Director provides sensor logs for debugging IBM System x serversrunning either Linux or Windows. Turning on one or more of these sensor logs canprovide 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 fileA 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 turnedon. IBM Systems Director is shipped with four sensor logs turned on and thereforeare four configuration files shipped with IBM Systems Director. You can create newconfiguration files to turn on additional logging.

The following configuration files are shipped with IBM Systems Director and arealready enabled for logging:v libipmi.cfgv libcommipmi.cfgv librsa.cfgv sensorw.cfg

To create a configuration file to enable additional logging, complete the followingsteps 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 IBMSystems Director installation. Note that this path uses the backslash (\) todelimit the directory; depending on the system that you are using, you mightbe required to enter the path using the forward slash (/).

2. If the configuration file for the log you want to enable was not shipped withIBM Systems Director, create the configuration file in the directory with theappropriate file name. To name the configuration file, use the file name of thelog file that you want to enable. Use .cfg for the file extension. For example, ifyou want to create a configuration file for the AssetIDProvider.log file, namethe configuration file AssetIDProvider.cfg. The following list provides all thevalid configuration file names.v AssetIDProvider.cfgv BlueLightProvider.cfgv blinterface.cfgv libcommrsa.cfgv libibm_shrdevice.cfgv libibmutils.cfgv spcommon.cfgv spinterface.cfgv IPConfigProvider.cfgv IPConfigInterface.cfgv PFAProvider.cfgv PFAInterface.cfgv SELProvider.cfgv SELInterface.cfgv SensorProvider.cfgv SmartProvider.cfgv SmartInterface.cfg

Troubleshooting and support 231

v raid_lsiadapter.cfgv scsi_smartadapter.cfgv ide_smartadapter.cfg

3. Open the configuration file and add the following lines:log=enablemaxlength=n

where n is the number (in MB) that you want to set for the maximum loglength.

4. Save and close the file.5. Stop Common Agent by typing the applicable command from the command

line and pressing Enter.

Option Description

Linux install_root/bin/twgstop

Windows net stop twgipc

where install_root is the root directory of your IBM Systems Directorinstallation.

6. (Windows only) Stop the winmgmt service by typing net stop winmgmt fromthe command line and pressing Enter.

7. (Windows only) Make sure that the Pegasus Provider Adapter process isstopped. Open the Windows Task Manager window and click the Processespage. If the Pegasus Provider Adapter process is still running, select the processfrom the list and then click End Process.

8. Start Common Agent by typing the applicable command and pressing Enter.

Option Description

Linux install_root/bin/twgstart

Windows net start twgipc

where install_root is the root directory of your IBM Systems Directorinstallation.

9. (Windows only) Start the winmgmt service by typing net start winmgmt fromthe command line and pressing Enter.

Related information:

AIX Pegasus CIM server and providers

Activating logging by creating an empty log fileYou can automatically activate sensor logging by creating an empty log file. Unlikeusing configuration files, you do not have to restart any services for the logging totake 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 thesupported log files on a managed system.

Operating system Batch file

Linux install_root\proddata\logging\createLogFiles.sh

Windows 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

232 IBM Systems Director Troubleshooting and Support Guide

the system that you are using, you might be required to enter the path using theforward slash (/).

In the batch file you can comment out log file names that you do not want tocreate 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 followingsteps 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 IBMSystems Director installation. Note that this path uses the backslash (\) todelimit the directory; depending on the system that you are using, you mightbe required to enter the path using the forward slash (/).

2. Create the log file in the directory with the appropriate file name. See “Sensorlogs for debugging” for the log file names.

3. Save and close the file.

Sensor logs for debuggingIBM Systems Director provides a number of log files for logging debuginformation for sensors in an IBM Systems Director environment.

The following log files are turned on by default for first failure data capture:v libipmi.logv libcommipmi.logv librsa.logv sensorw.log

Technical Support will tell you which of the following log files to turn on to gatherthe applicable data for your problem:

Asset IDReads and writes computer asset information and reads computer details,component information, and firmware levels: AssetIDProvider.log

BlueLightControls the front panel blue light:v BlueLightProvider.logv blinterface.log

IPConfigReads and writes IP configuration information for service processors:v IPConfigProvider.logv IPConfigInterface.log

PFA Predictive Failure Analysis (PFA) displays system DIMM information andgenerates events (alerts) if microprocessors (CPUs) or DIMMs arepreparing to fail:v PFAProvider.logv PFAInterface.log

SEL Reads and clears the service processor event log:v SELProvider.logv SELInterface.log

SensorReads the system environmental sensors and generates an event (alert) ifsomething goes wrong:v SensorProvider.log

Troubleshooting and support 233

v sensorw.log

SMARTReads drive information and generates an event (alert) if a drive ispreparing to fail. There is a separate log file for each type of physicalinterface:v SmartProvider.logv SmartInterface.logv raid_lsiadapter.logv scsi_smartadapter.logv ide_smartadapter.log

v The following log files are used by the libraries that communicate with anRemote 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 byproviders, interfaces, and service processor libraries.

Getting help and supportIf you need help, service, or technical assistance, or if you just want moreinformation, you will find a wide variety of sources available to assist you. Thissection contains information about where to go for additional information, andwhom to call for service, if it is necessary.

Finding information about IBM Systems Director problemsIn addition to the IBM Systems Director information center, you can findinformation about problems and solutions in earlier editions of IBM SystemsDirector documentation, the IBM Systems Director forum, and the Service Bulletin(RETAIN® tip) index.

Available troubleshooting documentation for earlier versions ofIBM Systems DirectorTo troubleshoot problems that are specific to earlier versions of IBM SystemsDirector, see the documentation for that version.

Notes:

1. Printable PDFs for the different versions of the IBM Systems Directordocumentation are available on the Resources tab of the IBM Systems DirectorWeb page: www.ibm.com/systems/management/director/.

2. IBM Director versions 4.22 and earlier and all versions of 5.10.x are no longersupported.

234 IBM Systems Director Troubleshooting and Support Guide

IBM SystemsDirector version Available troubleshooting documentation

6.2.x v IBM Systems Director version 6.2.x information center athttp://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp

v Release Notesv Service Bulletin (RETAIN tips) index

6.1.x v IBM Systems Director version 6.1.x information center athttp://publib.boulder.ibm.com/infocenter/director/v6r1x/index.jsp

v Release Notesv Service Bulletin (RETAIN tips) index

Accessing the IBM Systems Director customer forumThe IBM Systems Director customer forum provides a place for customers to shareideas and solutions for IBM Systems Director implementations. It serves as theforum for IBM Systems Director installations on all supported operating systemsand hardware.

Although participating in the customer forum does not guarantee an answer froman IBM representative, the forum community does include IBM employees that useIBM Systems Director. To access the IBM Systems Director Forum Web page, youmust sign in to the IBM developerWorks® Web site and create a profile; there is nofee.

Accessing the IBM Service Bulletin (RETAIN tips) indexYou can access the IBM Service Bulletin (RETAIN tips) index to view knownproblems and workarounds for IBM Systems Director.

Note: As of November 21, 2008, no new RETAIN tips are created for IBM SystemsDirector and related plug-ins. Instead, tips are now created as Technotes and areavailable in the IBM Systems Director Knowledge Base at www.ibm.com/support/search.wss?rs=0&q=eServerOnDemandKBRCH&r=100&sort=desc. All previous IBMSystems Director RETAIN tips continue to exist and were not migrated toTechnotes.

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 and System x hardware. ForIBM Systems Director articles about other hardware platforms, such as IBMPower® 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.

Troubleshooting and support 235

Getting support information from the World Wide WebOn the World Wide Web, the IBM Support Portal Web site has up-to-dateinformation about IBM BladeCenter, IBM Power, System x, and System z products,services, and support.

You can access the IBM Support Portal Web site at http://www.ibm.com/support/entry/portal/Overview.

Also, you can find information about IBM Systems Director in the Systems forumat www.ibm.com/developerworks/forums/forum.jspa?forumID=759.

Information to provide to the IBM Technical Support CenterWhen looking for assistance from the IBM Technical Support Center, there is somebasic information that you should provide.

Before you contact IBM for assistance, gather the following information for theaffected systems.

Note: Run the logcollector script to collect log files immediately following theissue. Log files wrap after a certain amount of data is collected, so important datamight be lost if you wait too long.v Machine types of all the affected systems.v Operating system.v Databases that you are using.v Approximate number of systems that IBM Systems Director manages.v Details about any changes to the hardware or software configuration that

occurred on the affected systems before the failure.v BIOS and firmware version levels of the affected systems.

Note: If you do not know this information and are on a System x system, youcan use Dynamic System Analysis (DSA) to gather the information for you. DSAis available from the Systems Management Web page at www.ibm.com/systems/x/solutions/management/resources/.

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 Detailed, step by step instructions for recreating the problem.v Any applicable screen shots.v The Virtual I/O Server version level, if you are running it on an AIX system.v The /var/log/localmessages file or any related log file on any manageability

access points (MAPs) for z/VM.v The /opt/ibm/director/log/TWGRas.log file on any System z management

servers.v Log files collected from the logcollector script. If the logcollector script was

not run, collect the following information instead:– Version of IBM Systems Director that is installed.– Whether the installed version of IBM Systems Director is a new installation or

an upgrade installation. If it is an upgrade installation, also determine theversion of IBM Systems Director from which you upgraded.

– 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 Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

236 IBM Systems Director Troubleshooting and Support Guide

– Installation logs, if you are experiencing an installation problem, that arelocated in the standard system directories and the install_root/logsdirectory.The following table contains examples of the installation logs that are locatedin the standard system directories.

Table 10. Examples of installation and uninstallation logs and their default locations

AIX and Linux logs

IBM Systems Director installation log: /var/log/dirinst.log

Platform Agent installation log: /var/opt/ibm/platform/log/install.log

Platform Agent uninstallation log: /var/opt/ibm/platform/log/uninstall.log

Windows logs

IBM Systems Director installation log: C:\Windows\dirinst.log

Platform Agent installation logs: C:\Windows\platinst_*.log

Platform Agent uninstallation logs: C:\Windows\platuninst_*.log

– Hardware logs, if you are experiencing a hardware failure or related issue.For more information, see “Providing hardware-log information” in the IBMSystems Director Systems Management Guide.

– Files containing the redirected output from the following commands:For AIX

- oslevel -r- prtconf- df -m

For Red Hat Enterprise Linux- cat /etc/redhat-release- rpm -qa- lsvpd

For SUSE Linux- cat /etc/SuSE-release- rpm -qa- lsvpd

Getting fixesOccasionally, new releases and upgrades are made available from the Support Website at www.ibm.com/systems/management/director/. These releases andupgrades might contain fixes to problems with IBM Systems Director.

If your IBM Systems Director environment has a problem that is not fixed by anew release or upgrade, contact the Technical Support Center. To do so, you musthave purchased an appropriate support product.

Service and support informationService and support offerings for IBM Systems Director are available on the IBMSupport Portal.

The IBM Support Portal is a unified, centralized view of all technical support toolsand information for all IBM systems, software, and services. The IBM SupportPortal lets you access the IBM electronic support portfolio from one place. You cantailor the pages to focus on the information and resources that you need forproblem prevention and faster problem resolution. Familiarize yourself with theIBM Support Portal by viewing the related demo videos at https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos. These videos introduce you to

Troubleshooting and support 237

the IBM Support Portal, explore troubleshooting and other resources, anddemonstrate how you can tailor the page by moving, adding, and deleting portlets.

MessagesEach message in IBM Systems Director and its plug-ins has a unique identifier (forexample, ATKSRV614E). You can use this identifier to find more detailedinformation in the information center.

You can use the Search feature of the information center or help system to searchfor additional information associated with your message. Copy and paste yourmessage identifier into the Search field, and click Go. Note that not all messageshave more detailed help associated with them.

The messages are structured as follows: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, as follows:

E Indicates that the message is an error message.

I Indicates that the message is an information message.

W Indicates that the message is a warning message.v Zero padded numbers are not unique. Numbers 29, 029, and 0029 are all the

same.

238 IBM Systems Director Troubleshooting and Support Guide

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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

© Copyright IBM Corp. 1999, 2012 239

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationDept. LRAS/Bldg. 90311501 Burnet RoadAustin, TX 78758-3400U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,

240 IBM Systems Director Troubleshooting and Support Guide

modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

Other company, product, or service names may be trademarks or service marks ofothers.

INFINIBAND, InfiniBand Trade Association, and the INFINIBAND design marksare trademarks and/or service marks of the INFINIBAND Trade Association.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiariesin the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Othernames may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 241

242 IBM Systems Director Troubleshooting and Support Guide

����

Printed in USA

GC30-4177-05