IBM Support

/opt/pconsole/README from AIX 6 Product

  Readme


  README for IBM Systems Director Console For AIX Version 6.1.0

This README contains information that was determined late in the
development cycle and could not be put in the regular publications.


      Limitations


        Flash

The Health application uses Flash  to display data in a pie-chart. Flash
is not available on AIX so the data is displayed in a table instead. If
you are not running on AIX and Flash is not installed in your browser,
you will see empty space where the pie-chart should appear.


      Known Problems

The Firefox browser for AIX requires a fix from Java which will be in
Java 5 Service Release 6.

The console includes a browser applet that requires Java 5.

The graph that is drawn in the Health Metrics Detail portlet is
dependent upon Flash. If Flash is not installed on Windows or Linux, the
Metrics Detail portlet will be empty.




      Updates to the IBM Systems Director Console for AIX Administration
      Guide

Note: The AIX authorizations identified in this table may not be
sufficient for all of the subtasks within a task category. For example,
some of the subtasks may run scripts or access files that have not been
enabled for enhanced RBAC authorizations.

*Task*                     *Console Role*       *AIX Authorizations*

Health                     aixHealth            aix

Software Installation      aixSoftware          aix.system.install
and Maintenance                                 aix.system.stat
                                                aix.system.boot
                                                aix.network.config

Software License           aixLicenses          aix
Management

Devices                    aixDevices           aix.device

System Storage             aixStorage           aix.fs
Management                                      aix.lvm

Security & Users           aixUsers             aix.security.user
                                                aix.security.role
                                                aix.security.group
                                                aix.security.passwd

Communication Applications aixNetwork           aix.network
and Services

Workload Partition         aixWorkloadPartitions aix.wpar
Administration

Print Spooling             aixPrinters          aix.device.config.printer
                                                aix.device.stat.printer

Advanced Accounting        aixAdvancedAccounting aix.system.config.acct

Problem Determination      aixProblemDetermination aix.ras
Performance & Scheduling   aixPerformanceAndScheduling  aix.system.stat
                                                aix.system.config.init
                                                aix.system.config.perf
                                                aix.system.config.cron
                                                aix.system.config.wlm
                                                aix.system.config.dlpar
                                                aix.proc.status
                                                aix.ras.trace

                                                aix.network.config.no
System Environments      aixSystemEnvironments  aix.system
                                                aix.ras.dump
                                                aix.ras.error
                                                aix.device.manage.change

Processes & Subsystems  aixProcessesAndSubsystems aix.proc
                                                aix.system.config.src

SMIT - Classic View        aixSMITclassic       aix (Note: This authorization
                                                is equivalent to root
                                                authority).

DCEM                       aixDCEM              N/A


Role Based Access Control  aixRBAC              aix.security

Web-based System Manager   aixWebSysMgr         Not applicable. The Web-based
                                                System Manager can be launched
                                                from the console (when the
                                                setup steps have been
                                                completed), however, it does
                                                not run within the console. The
                                                setup steps include tasks in
                                                the Software Installation and
                                                Maintenance and the System
                                                Environments applications,
                                                which require the
                                                authorizations listed for
                                                those applications.





      Other Useful Information


        Language Selection:

The language environment of a session is determined by your browser's
language preferences, the available languages installed on the managed
machine and your AIX account's LANG setting in your ~/.profile or
/etc/environment. The installed languages for bos.help.msg are used to
determine what languages are available. The first language on your
browser's preference list that is installed is used. If your LANG
setting is for that language, then the closest matching installed
codeset, country code and variant will be used. Otherwise a preference
is given to UTF-8 codesets.

Not all messages have been translated to every language. Untranslated
messages will appear in English. This is consistent with SMIT behavior.
The translated messages come from multiple installable images, depending
on the features involved. Be careful to install the needed language(s)
using the System Environment Plug-in. Some English messages are not
installed by default. They must be installed as part of the en_US or
EN_US locale.


      Troubleshooting:


        Connection problems:

Issue- My connection keeps timing out when trying to connect to the console
       URL.

Try to telnet to the server to make sure it?s not behind a firewall.
Since the console is not on port 80, you may not be automatically
prompted for your firewall credentials.


Issue- My session keeps invalidating.

Since the console only allows one instance per user, somebody could be
logging in with the same username and invalidating your session.


Issue- The console is very slow to load the first time I launch it.

If you are connecting to a WPAR, the console runtime is not started
until the first connection. The pconsoleProxy subsystem intercepts the
request and starts the console runtime. Verify that the pconsoleProxy
subsystem is active. You can query the status of the pconsoleProxy
subsystem by running:
   lssrc -s pconsoleProxy
You can query the status of the pconsole subsystem by running:
   lssrc -s pconsole


Issue- When I try to connect to the console URL, I get an "Unable to Connect"
or "the page cannot be loaded" message.

Check whether the console subsystem is active by running
  lssrc -s pconsole
If it is not active, try to start it by running
  startsrc -s pconsole
If it does not start and you get a message such as: "The pconsole
Subsystem could not be started. The Subsystem's user id could not be
established. Please check the Subsystem's user id and try again.",
check that the pconsole user account has not been removed and that the
UID matches the UID that owns the files under /pconsole. If the user
account is missing, reinstall sysmgt.pconsole.rte so that the account is
recreated with the required attributes. If the user account exists, but
the UID is incorrect, remove the user account and reinstall
sysmgt.pconsole.rte. For more information, see "If you accidentally
delete the user pconsole" below.



        If the task you are trying to execute fails:

Many of the tasks in the OS Management category are based on SMIT. If a
task fails in the console, try the task in SMIT or smitty to see it it
also fails there. Log in to the system on a local terminal or via telnet
and try the task in SMIT/smitty. If it also fails in SMIT/smitty, then
the problem may be in SMIT or in the commands or scripts executed by
SMIT.  Use the "Show Command" function (F6) to show the command and if
possible try to perform the task using the command line to see if the
failure is caused by the command or by SMIT/smitty.


        Login (Authentication) problems:

   1. If someone is already logged into the console with the same user
      id, authentication will fail. The console allows only one session
      per user-id, per system. The console gives you the option of
      ending the current session and starting a new one, or waiting
      until it is ended by the person who initiated it.
   2. Verify that the user has an account on the system you are
      connecting to. To do this, login to the system and list all users.
      If the user is not listed, add them to the system.
   3. Verify that the user's password has not expired. If the user does
      not have a password (for example, if it is a new account) or if
      the password has expired, the user will not be able to log in to
      the console. To resolve this, the user must log in to the system
      via telnet or a local terminal and set the password.


        If tasks appear to be missing from the  navigation area:

You will not be able to see tasks in the navigation area unless your
login id has been added to the console roles. The console administrator
id (usually root) can add users to console roles. When you are logged in
as console administrator (by default root) all tasks are visible.


         If you get AIX authorization errors when performing a task:

If you are not logged in as root and enhanced RBAC is enabled (it is
enabled by default), most administrative commands require you to have
specific aix authorizations. If you encounter authorization errors
please try the following:

    * Check that you have the authorizations required for the task and
      that they are active by using the My Active Roles application.
    * Try the task using smitty or on the command line to determine if
      the authorization errors also occur outside of the console.
    * If you discover that authorizations are needed for the task, but
      they are not documented in the console admin guide or readme file,
      add the authorizations to your roles. Open a problem report so the
      lab can fix the documentation and the application's authorization
      descriptor.
    * If  you discover administrative tasks that fail because they are
      not instrumented for enhanced RBAC (e.g. they have hard coded
      checks for root or uid 0), open a problem report so the lab can
      fix the code


        If you accidentally delete the user pconsole:

All of the files belonging to IBM Systems Director Console for AIX
belong to the userid pconsole. On most machines (those running with
Enhanced RBAC) the console runs as the user pconsole. If you delete this
user, then the console will not be able to run. If pconsole's user id
and group id has not be re-used for some other purpose you can recreate
the pconsole user and group by specifying the original ids. You can see
the ids by:

    #ls -l /pconsole

If recreating the pconsole user and group does not work then you should
reinstall the console, using the original installation media via:

#installp -agXd <install device> sysmgt.pconsole


        If you don't see all of the menus that you see in smitty:

This is most likely due to additional software being installed after the
console was started. You should restart the console as root with:

    #stopsrc -s pconsole
    #startsrc -s pconsole


        Filesystem fills up:

Log files for the console are stored in /var/log/pconsole. In addition,
each user of the console will have a wsmit.log and wsmit.script file in
their home directory. Deleting these files will not free up memory until
the user logs out of the console, however instead of deleting the file
you empty it via:

    #echo "" > <path_to_log_file>

Additional files are stored in $HOME/dcem. These files include output
results, scripts and command specs.


        Editor problem:

There are a small number of  instances where a user is placed in an
editor while in the SMIT Command Output panel. There is a problem with
the console's terminal emulator that causes the vi paste command (Esc + p)
to paste a blank line instead of what is in the paste buffer.


        Issues Unique to DCEM:


Issue- I'm unable to execute new jobs, generate scripts, or save command
specification.

Check to see if any of the filesystems have run out of free space.  DCEM
stores command specs, results, and scripts in $HOME/dcem.

Issue- Executing jobs with DCEM is filling up my filesystem.

DCEM stores all of the output/results in $HOME/dcem. If you're executing
jobs that produce a lot of output, you may need to increase your $HOME
filesystem size.

Issue- All of my jobs are failing and the output says that "Permission is
Denied."

Make sure you have the correct permissions by executing a job via the
command line. Also, the shell that you?re using for authentication on
the remote hosts (rsh or ssh) must be specified on the ?Options? tab in
DCEM.



        Issues Unique to Role Based Access Control application:


Issue- Task links on the Role Based Access Control application Welcome Page are
not active.

Check that enhanced RBAC is enabled by running the
  lsauth ALL
command.  If enhanced RBAC is enabled, authorization attributes will
be listed and the return code will be 0.

Check that you are logged into the console as the console administrator.


Issue- The roles and authorizations that I have added have not taken effect.

Run the Synchronize Data task to update the RBAC Security Table.
Then have the user log in and activate their new or modified roles using
the swrole command.




      Configuration

The default maximum memory heap size for IBM Systems Director Console
For AIX  is 512MB. This can be configured by editing
/pconsole/lwi/conf/overrides/pconsole.javaopt.


      WPAR Environment

IBM Systems Director Console For AIX is not installed on each WPAR by
default. In order to enable system management for AIX instances within a
WPAR, you must use the wparConsole.sh utility. The IBM Systems Director
Console for AIX will be installed on all newly created system WPARs if
you execute the following:

   #/opt/pconsole/bin/wparConsole.sh -e

To disable the installation of the console within system WPARs,  execute
the following:

   #/opt/pconsole/bin/wparConsole.sh -d

The default size of the root file system within a WPAR is not large
enough for the console. To increase the file system size when creating
a wpar, pass the following paramaters to the mkwpar command:

   #mkwpar -M directory=/ size=128M ...

If the system WPAR has already been created, you can manually increase
the size of the root file system from the GPAR using the 'chfs' command.
You may have to reinstall the sysmgt.pconsole.* filesets in the WPAR
if the console has been accessed prior to the size increase.

The enabling and disabling of the console on wpars only effects WPARs
created in the future. Refer to the documentation for the 'syncwpar'
command on how to synchronize preexisting WPARs.



        ProxyServer

In order to reduce the start-up resources of the console in a WPAR
environment, the console is not started until someone tries to connect
to it. All HTTP requests to the console are routed to a proxy which will
start the console (if needed) before forwarding the request to the
console. To see if the proxyServer is configured on your system enter
the command:

   #lssrc -g pconsole

For systems with the proxyServer you will see two lines. One for the
pconsoleProxy subsystem and another for the pconsole subsystem. In
addition, the /etc/inittab file will have an entry to start
pconsoleProxy subsystem instead of pconsole. To manually enable the
pconsoleProxy on a system that already has IBM Systems Director Console
for AIX installed run the command:

   #/opt/pconsole/bin/pconsole_config -enable

To disable the proxy so that the console is started at system boot run
the command:

   #/opt/pconsole/bin/pconsole_config -disable

Further,  when the proxy is configured, the console is configured to use
ports 5337 and 5338 while the proxy uses 5335 and 5336. These values can
be changed by editing /pconsole/lwi/conf/overrides/port.wpar.properties,
/pconsole/lwi/conf/webcontainer.properties and
/opt/pconsole/bin/pconsole_config.

Please note that the response to first connection to the proxy will be
significantly delayed until the console is started. Subsequent requests
should not be delayed.



Document information

More support for: AIX family

Software version: 610

Operating system(s): AIX

Reference #: 610readmea97965ebt_p
console

Modified date: 01 May 2008


Translate this page: