CommandPointTM for Tivoli® TME10TM V1.0.0 Release Notes


Introduction

CommandPointTM for Tivoli® TME10TM is a Tivoli/Plus module that provides access to NUMA-Q®-specific administrative capabilities. It allows customers using the Tivoli Management EnvironmentTM (TME 10) to monitor NUMA-Q-specific events and performance metrics. It also provides a launch point for various utilities and tasks often used by system administrators.

These Release Notes contain the following information:


Compatibility Information

CommandPoint for Tivoli TME10 V1.0.0 is compatible with the following software products running on Symmetry® and NUMA-QTM systems:

CommandPoint for Tivoli TME10 V1.0.0 is compatible with Tivoli TME V3.0.1 and other Tivoli products that are compatible with Tivoli TME V3.0.1.


ATTENTION

Refer to Tivoli documentation for hardware system requirements.



Installation and Setup


Installation

Tivoli TME10 framework and its applications, Distributed Monitors (Sentry) and Software Distributions (Courier) should be installed before you install CommandPoint for Tivoli TME10.

CommandPoint for Tivoli TME10 uses Tivoli/Plus installation. Refer to the Tivoli documentation for installation information. The CommandPoint for Tivoli TME10 software is on the Systems Management Software CD.


ATTENTION

Tivoli TEC V3.0 or V3.1 does not run on DYNIX/ptx. If you want to run Tivoli TEC, you have to set up another TMR server running on a Windows NT® V4.0 or a Solaris® system.



ATTENTION

Tivoli TME does not have a deinstall command. Therefore, before installing CommandPoint for Tivoli TME10, you should back up the Tivoli TME database, in case you later want to deinstall CommandPoint for Tivoli TME10 and restore your system to its prior state.


The CommandPoint for Tivoli TME10 image directory contains the following files:


Configuring and Distributing the CommandPoint for Tivoli TME10 Filepackage

After installing CommandPoint for Tivoli TME10, you need to configure and distribute the CommandPoint for Tivoli TME10 Filepackage to all clients. The following steps describe how to proceed:

  1. From the CommandPoint for Tivoli TME10 window, double click on the icon labeled "Configure CPTME Filepackage" to prepare a file package for distribution. A dialog box will appear, requesting the source host and source directory (such as <cdrom device>/cptme/cptmefiles). Enter the source host name where the CommandPoint for Tivoli TME10 file package is going be distributed from and enter the source directory (path) where CommandPoint TME utility files are located.


    ATTENTION

    If you do not know your source host name, at a UNIX® prompt enter wls <region name> to get a list of the source host's name.


  2. Right-click on the CP for TME Filepackage icon and select Open. In the File Package Properties window, click on the "Change mode of source files to" button and enter 777 and click on Save & Close.

  3. Right-click on the CP for TME Filepackage icon and select Subscribers. Move all the clients to the Current Subscribers section of the window.

  4. Right-click on the icon labeled CP for TME Filepackage and select Distribute to distribute CommandPoint for Tivoli TME10 utility files to all CommandPoint for Tivoli TME10 clients.


ATTENTION

This last step should create /usr/cptme/bin and /usr/cptme/log directories and distribute files into these directories. You should verify that the distribution was successful on all subscribers you selected. If these directories do not exist, repeat the configuration and distributions steps.


This procedure is described in more detail in Chapter 2 of the CommandPoint for Tivoli TME10 User's Guide.


Configuring TEC V3.11 on Windows NT 4.0 for Event Processing


ATTENTION

If you have TEC running on Windows NT 4.0, you need to configure Windows NT for event processing.



ATTENTION

This section assumes that you have TEC v3.11 and Tivoli Distributed Monitors (Sentry) installed on a different TMR than the TMR that is managing the DYNIX/ptx system(s).


To configure TEC V3.11 on Windows NT 4.0, perform the following steps:

  1. Copy the entire tecsetup directory on the System Management Software CD on to the Windows NT system that is running TEC event server.

  2. Open a BASH shell by entering the following command at a DOS prompt:

    c:\Tivoli\bin\w32-ix86\tools\bash.exe.

    The drive name may vary depending on where you installed Tivoli.

  3. Set up the Tivoli environment for the BASH shell by entering a command to source the environment. For example, depending on your system setup, you might enter:

    . c:/winnt/system32/drivers/etc/tivoli/setup_env.sh

  4. Change directory to tecsetup/cptme directory and run the following command:

    ./cpcfg_tec.sh &lt;UseNew> &lt;UseExisting> &lt;ExistingRulebase> &lt;NewRulebase> &lt;CloneRulebase> <&lt;RulebasePath> &lt;EventConsole>

    where the following values apply:

    UseNew = on/off
    UseExisting = on/off
    ExistingRulebase = Name of the rulebase if UseExisting is on, otherwise use ""
    NewRulebase = Name of the rulebase if UseNew is on, otherwise use ""
    CloneRulebase = Name of the rulebase that this rulebase will be clone from.
    RulebasePath = the path for this new rulebase
    EventConsole = the Event console name.
    

For example, you might enter:

./cpcfg_tec.sh on off " " "mytestRulebase" "Default" "c:/myrb" "Root_elm8a60-region"


Configuring the Logfile Adapter

To configure the Logfile Adapter to work with the event server, double click on the Configure Logfile Adapter icon.

If you need to verify or change subscribers for the Logfile Adapter, do the following:

  1. Click on the Configure Logfile Adapter icon.

  2. Select Modify job.

  3. Move Nodes to which you want to subscribe into the Selected Task Endpoints section of the window.

  4. Click on Change &amp; Close.

The Logfile Adapter is described in the Tivoli documentation.


Deinstallation

Tivoli TME does not have a deinstall command. Therefore, before installing CommandPoint for Tivoli TME10, you should back up the Tivoli TME database, in case you later want to deinstall CommandPoint for Tivoli TME10 and restore your system to its prior state. Tivoli TME databases are located in the /var/spool/Tivoli/backkups directory.

To manually deinstall CommandPoint for Tivoli TME10, do the following:

  1. Execute the following commands to restore the Tivoli TME object database:

    #wbkupdb -r -d &lt;database_name>

    #wchkdb -u

  2. Copy the Uninstall script from the System Management Software CD to all nodes on which you installed CommandPoint for Tivoli TME10 as follows:

    #cp/&lt;cd-device>/cptme/cptmeimage/Uninstall_cp.sh /tmp/Uninstall_cp.sh

  3. Change the mode of the file by entering the following:

    #chmod 777 /tmp/Uninstall_cp.sh

  4. Execute /tmp/Uninstall_cp.sh.


Problem Reports

The number that appears in parentheses in problem report titles is the internal number assigned to the report. These problems will be corrected in a future release unless otherwise noted.


Add Monitor Lets You Add Non-Existent Devices (238294)

Add Monitor doesn't do any argument verification. For example, when prompted for diskid, you could enter an invalid disk device.

Workaround. None.


Configure CP for TME Filepackage Receives an "Invalid Error" Message (238180)

Upon executing Configure CP for TME Filepackge, a return code of 0 (zero) is returned and the stdout message indicates successful configuration. However, the src_host and src_path also appear in stdout and they should be suppressed.

Workaround. None.


Uninstall Script Does Not Remove /usr/cptme Directory (238182)

The Uninstall_cp.sh script from the System Management Software CD does not remove /usr/cptme.

Workaround. Manually remove /usr/cptme.


Online Help for CleanTmpFile Contains an Error (238193)

The help file for the task CleanTmpFile contains misleading information. It states:

Cleans out files in /tmp and /usr/tmp that are older than a certain date.

The task does not clean out file(s) in /usr/tmp.

Workaround. None.


ListMonInstanceName Task for Ethernet Devices on NUMA-Q Has Incorrect Output (238185)

The ListMonInstanceName task output for EthernetTM devices on NUMA-Q lists devices that do not exist.

Workaround. For Ethernet devices, use dumpconf | grep pe


RemoveExpiredKtlog Task Output Does Not Display If Task Successful (238187)

The RemoveExpiredKtlog task does not display an output if the task is successful.

Workaround. Manually verify that the file(s) have been removed from the /usr/adm/ktlog/ directory specified in the log_dir field.


SetAutoDump Task Output Is Misleading (238188)

The SetAutoDump task successfully changes the bootflags, but it prints an error messages indicating that an error has occurred.

Workaround. Enter # bootflags -bh to verify the bootflag change.


TruncateCPTMEeventlog Task Output Is Misleading (238189)

The TruncateCPTMEeventlog task returns a No such process! message, when in fact the task works.

Workaround. None.


The SndMsg Task Is Unable to Determine the Sending tty (238196)

The SndMsg task is unable to determine the TTY (terminal) that the message was sent from (the message is sent, however).

Workaround. None.


Selecting Run on Selected Subscribers Kills Tivoli (238445)

Selecting Run on Selected Subscribers from the Configure Logfile Adapter icon kills Tivoli. The oserv must then be restarted from the /etc/rc2.d/S99Tivoli script.

Workaround. To verify or change subscribers:

  1. Click on the Configure Logfile Adapter icon.

  2. Select Modify job.

  3. Move Nodes to which you want to subscribe into the Selected Task Endpoints section of the window.

  4. Click on Change &amp; Close.