−Table of Contents
IBM System Director (no longer supported)
IBM System Director is able to monitor hardware, software updates (deployment), firmware updates, and much more.
For information, 4GB RAM is not enough.
Installation on AIX server, it's not supported on WPAR. IBM director can manage IBM servers Blade, Intel, Power, Mainframe, and other hardware but not for free. For IBM servers it's free except advanced functions.
Uninstall System Director
on VIOS
To stop the common and platform agents, run the following command:
/opt/ibm/director/agent/bin/stopagent_vios cimserver -s
Uninstall the nonstop service by running the following command:
/opt/ibm/director/agent/runtime/nonstop/bin/installnonstop.sh -uninstallservice
on AIX
To permanently uninstall the Director agent or server components and leave the filesets that might be used by other applications, run the following command:
/opt/ibm/director/bin/diruninstall
It will uninstall the following filesets:
DirectorServer (if Director server was installed) DirectorCommonAgent DirectorPlatformAgent
To uninstall the filesets that remain after running diruninstall command, do the following:
installp -u cas.agent # Uninstall common agent services (1) installp -u tivoli.tivguid # Uninstall Tivoli Guid installp -u sysmgt.cim.*providers* # Uninstall all CIM providers installp -u sysmgt.cimserver.pegasus.rte # Uninstall Pegasus CIM server (2)
If there is no diruninstall script, you need to manually uninstall the Director filesets to recover from a failed install using the following commands:
installp -C # Clean up possible unfinished install installp -u DirectorServer # Uninstall Director server - Only if the server is installed installp -u DirectorCommonAgent # Uninstall Director subagents (aka Common Agent) installp -u DirectorPlatformAgent # Uninstall Director Platform agent
Install IBMdirector
Once uncompressed, go into the directory, the package can be installed with default values, else use the response file: <box 100% round orange|>./dirinstall.server</box>
Now you are ready to configure IBM System Director, Resource Manager username is not the login password. Use a user that is still defined on your server. Best way is to leave a blank password, it will be automatically generated by application:
[root@monitor]/gpfs1/srv# /opt/ibm/director/bin/configAgtMgr.sh Enter 1 to use the Agent Manager installed with this server (recommended) Enter 0 to use an existing Agent Manager (advanced) : 1 Enter Resource Manager username : dirinst1 Enter Resource Manager password : Re-Enter Resource Manager password : Enter Agent Registration password : Re-Enter Agent Registration password : [Add] [Element]: AgentManagerUserID [Value]: dirinst1 [Add] [Element]: AgentManagerPassword [Value]: {aes:3C5SnKQL63SjkEy44Gs+vHF6nQzC+Dil1NzNvSiAzzk=}20YlY60UOpRYxP7rKJXcmw== [Add] [Element]: ManagerRegistrationPassword [Value]: {aes:3C5SnKQL63SjkEy44Gs+vHF6nQzC+Dil1NzNvSiAzzk=}20YlY60UOpRYxP7rKJXcmw== DataSourceConfig.sh=0
Now you are ready to start IBM System Director (about 5 minutes to be up and running): <box 100% round orange|> [root@monitor]/root# /opt/ibm/director/bin/smstart </box>
Check the status: <box 100% round blue|> [root@monitor]/root# /opt/ibm/director/bin/smstatus
Active </box>
Once activated, you can connect on:
http://<ip_server>:8421/ibm/console or https://<ip_server>:8422/ibm/console
Logs directories:
/opt/ibm/director/logs /opt/ibm/director/lwi/logs
In case of trouble, check the status of websphere into lwi logs (most problems)
[root@monitor]/opt/ibm/director/lwi/bin# ./lwistatus.sh ALR0450W: Waiting for connection to the administration port. 33782 ALR0450W: Waiting for connection to the administration port. 33782 ACTIVE [root@monitor]/opt/ibm/director/lwi/bin# ./lwistatus.sh ACTIVE
<box 100% round orange|Error:>
ATKMDL001E The required Universal Systems Management Services are not available. Log out of the management server and login after a few minutes.
Leave password blank, it will be generated [root@monitor]/opt/ibm/director/bin# ./changePassword.sh </box>
