-------------------------------
HP Instant Toptools 5.54 readme
-------------------------------

This readme contains an overview and known issues for HP Instant Toptools for
Linux.

Versions Supported:

HP Instant Toptools 5.54
- Red Hat 8.0

HP Instant Toptools 5.53
- Red Hat 7.2
- Red Hat 7.1
- SuSE 7.3
- SuSE 7.2
- Turbolinux 6.5
- Caldera OpenLinux Server 3.1
- Debian 2.2

Manageability Technical Information is available on the web at:
http://netserver.hp.com/netserver/support/manaq_technical_info.asp

The purpose of this document is to insure that you are aware of the latest
information for HP Instant Toptools. To check for periodic updates, go to
http://www.hp.com/toptools.



--------
Contents
--------

1. Release Notes
2. Overview
3. Installation
4. Uninstall
5. Accessing HP Instant Toptools
6. Browser Settings
7. Resolving IP PORT Conflicts
8. Known Issues


-----------------
1.  Release Notes
-----------------

1.1 New Features:

    1. First release for Red Hat 8.0 version.

1.2 New Linux distributions supported:
    - Red Hat 8.0

1.3 New Linux kernels supported:
    - Red Hat 8.0
        2.4.18-11
        2.4.18-11smp
        2.4.18-14
        2.4.18-14smp

------------
2.  Overview
------------

HP Instant Toptools is a standalone browser-based tool for monitoring your HP
Server. HP Instant Toptools provides web pages that include information
about the current state of an HP Server to assist in troubleshooting.

All events (changes in the status of your server) are stored in your HP
Server's System Event Log. These events may be viewed while the server is up
and running by viewing the Event Log under the Status tab in HP Instant
Toptools.

NOTE:  HP Server Agents software shipped with your HP Server are required
for HP Toptools Device Manager. Server Agents are not required for Instant
Toptools. However, with the Server Agents installed you will additionally
be able to receive predictive events, on all HP mass storage events otherwise
only obtainable through HP Toptools Device Manager.

----------------
3.  Installation
----------------

3.1.  Before You Begin

Before starting the installation of the HP Instant Toptools on your HP Server,
verify that all requirements are satisfied.


3.1.1.  Hardware Requirements

This version of the HP Instant Toptools for Linux can be installed only on a
specific set of HP Server computers, listed below:

e 60, e 800,
lpr,
lxr 8500,
lc 2000, lc 2000r,
lh 3000, lh 3000r,
lh 6000, lh 6000r,
lt 6000r,
lp 1000r, lp 2000r

3.1.1.1. Hardware support added on release 5.02.07:

lc II,
lh 3, lh 3r,
lc 3,
lh 4, lh 4r,
lxr 8000

3.1.1.2. Hardware support added on release 5.02.09:

lh 6000 U3,
lc 2000 U3,
lh 3000 U3,
lt 6000 U3,
lp 1000r (1.13 and 1.26 GHz),
lp 2000r (1.13 and 1.26 GHz)

3.1.1.3. Hardware support added on release 5.52.00:

tc 3100,
tc 4100

3.1.2.  Hard Disk Space Requirements

The minimum amount of hard disk space needed for this installation is 8 MB.


3.1.3.  Software Requirements

In order to get information provided by the Motherboard Management Card (MMC)
or Remote Management Card (RMC) the HP Server Agents need to add a device
driver to the kernel. If you have one of the Linux distributions/kernels
supported (please, see section 3.1.3.1), this driver is already provided in the
mmcdev package, included in the distribution CD. Otherwise you must compile and
install the device driver. For more information on this, see section 3.1.3.2.

For information about how to upgrade the kernel, go to the link below:
http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html

For information about how to upgrade the RPM package, go to the link below:
http://www.redhat.com/support/errata/RHEA-2001-016.html


3.1.3.1 Linux distributions supported

This product needs the following software installed in the system to run:

For Red Hat 7.1:

- Kernel (one of the following):
     2.4.2-2
     2.4.2-2smp
     2.4.2-2enterprise
     2.4.3-12
     2.4.3-12smp
     2.4.3-12enterprise
     2.4.9-6
     2.4.9-6smp
     2.4.9-6enterprise
     2.4.9-12
     2.4.9-12smp
     2.4.9-12enterprise
     2.4.9-31
     2.4.9-31smp
     2.4.9-31enterprise
- RPM 4.0.2

For Red Hat 7.2:

- Kernel (one of the following):
     2.4.7-10
     2.4.7-10enterprise
     2.4.7-10smp
     2.4.9-7
     2.4.9-7enterprise
     2.4.9-7smp
     2.4.9-13
     2.4.9-13enterprise
     2.4.9-13smp
     2.4.9-31
     2.4.9-31enterprise
     2.4.9-31smp
- RPM 4.0.3

For Red Hat 8.0:

- Kernel (one of the following):
	2.4.18-11
	2.4.18-11smp
	2.4.18-14
	2.4.18-14smp
- RPM 4.1.0-34
- compat-libstdc++-7.3-2.96.110

For SuSE 7.2:

- Kernel (one of the following):
     2.4.4-4GB
     2.4.4-4GB-SMP
     2.4.4-64GB-SMP
     2.4.7-4GB
     2.4.7-4GB-SMP
     2.4.7-64GB-SMP
     2.4.16-4GB
     2.4.16-4GB-SMP
     2.4.16-64GB-SMP

For SuSE 7.3:

- Kernel (one of the following):
     2.4.10-4GB
     2.4.10-4GB-SMP
     2.4.10-64GB-SMP
     2.4.16-4GB
     2.4.16-4GB-SMP
     2.4.16-64GB-SMP

For Turbolinux Server 6.5:

- Kernel (one of the following):
     2.4.5-0.5
     2.4.5-0.5smp

For Caldera OpenLinux Server 3.1:

- Kernel:
     2.4.2

For Debian 2.2:

- Kernel:
     2.4.18-386
     2.4.18-686
     2.4.18-686-smp


3.1.3.2  MMC on not supported kernels

If your kernel is not supported, it will be necessary to compile the device
drivers and copy them manually to the directories specified below. The
sources of this device drivers are available at the HP website.
mmcdev.o:
   /lib/modules/`uname -r`/kernel/drivers/char/mmc/era/shared/driver/linux/
seldev.o:
   /lib/modules/`uname -r`/kernel/drivers/char/mmc/era/shared/seldev/linux/

NOTES:
1. If you have already installed the HP Instant Toptools on a system running
a not supported kernel, it will be necessary to completely remove and install
the product again.


3.1.4. Coexistence with other products

As of this writing there are no known coexistence problems with other
HP products.


3.2.  Installation Procedure

Before installing HP Instant Toptools on an HP Server running Linux, verify if
your platform satisfies the hardware and software requirements as listed above
in section 3.1. If all requirements are satisfied, just follow procedure
listed below for each supported distribution.

Note that package file names have the following format:

<package_name>-<version>.<patchlevel>-<release>_<distrib>.i386.<rpm>

As an example, itt-lx-5.02.02-03_rh71.i386.deb refers to the version 5.02,
patchlevel 02 and release 03 for Red Hat 7.1 of a package named itt-lx. Note
that <version> is composed by a major and a minor version numbers.

In the following sections the patchlevel, release and distrib fields will be
represented by letters xx, yy and zzz, respectively.

The HP Instant Toptools installation process will install all necessary files
and start services, which are registered for the automatic execution on the
next computer's initialization. No reboot is necessary after installation
process.

The package contains a hardware check procedure to verify if the Server
under use is supported by this HP Instant Toptools version. If not, a warning
message is displayed and the installation aborts.


IMPORTANT NOTICES:
++++++++++++++++++

    1. When updating Server core component (hpserver-core) from a version
       older than 5.02.08, first remove agents_lx, itt_lx and hpserver-core
       before proceeding with the installation:

       1.1 For distributions based on RPM (Red Hat, SuSE, TurboLinux and
           Caldera):

       To know the version of the hpserver-core package, type the following
       command:

           # rpm -q hpserver-core

       To remove agents_lx, itt_lx and hpserver-core execute the commands
       below:

           # rpm -e agents_lx
           # rpm -e itt_lx
           # rpm -e hpserver-core

       Notice that some data files will be removed, and Agents will not keep
       "Contact" and "Location" information.

       1.2 For Debian:

           To know the version of the hpserver-core package, type the following
           command:

               # dpkg -s hpserver-core

           To remove agents_lx, itt_lx and hpserver-core execute the commands
           below:

               # dpkg -P agents-lx
               # dpkg -P itt-lx
               # dpkg -P hpserver-core

    2. When updating the mmcdev package from a version older than 5.52.00 for
       Red Hat 7.2, or older than 5.02.02 for all other Linux distributions,
       first remove this package before proceeding with the installation:

       2.1 For distributions based on RPM (Red Hat, SuSE, TurboLinux and
           Caldera):

       To know the version of the mmcdev package, type the following
       command:

           # rpm -q mmcdev

       To be able to update this package remove it by typing the following
       commands:

           # rpm -e mmcdev

       2.2 For Debian:

           To know the version of the mmcdev package, type the following
           command:

               # dpkg -s mmcdev

           To be able to update this package remove it by typing the following
           commands:

               # dpkg -P mmcdev


    3. When updating Instant Toptools (itt_lx) from a version older than
       5.53.03-01 for Red Hat 8.0 first remove itt_lx and hpserver-core before
       proceeding with the installation:

       To know the version of the itt_lx package, type the following command:

           # rpm -q itt_lx

       To remove itt_lx and hpserver-core execute the commands below:

           # rpm -e itt_lx
           # rpm -e hpserver-core

       Notice that some data files will be removed, and Agents will not keep
       "Contact" and "Location" information.


3.2.1 Installing HP Instant Toptools

   3.2.1.1 For distributions based on RPM (Red Hat, SuSE, TurboLinux and Caldera):

   1. Download the zip file containing the appropriate HP Instant Toptools
   installation files for your version of Linux (the installation files
   are separated in directories named by distribution version). For Red Hat 8.0
   the version is 5.54. In steps below you should replace 5.53 by 5.54. 

   2. Expand the zip file containing the Instant Toptools to a temporary
      location on your Linux system (for example /tmp)
        # unzip -o <name_of_zip_file> -d /tmp
      for example,
        # unzip -o customer.zip -d /tmp

   3. Install the MMC device driver:
        # rpm -U /tmp/mmcdev-5.53.xx-yy_zzz.i386.rpm
        NOTE: if the MMC device driver is already built in kernel or
              installed as a kernel module, this package is not needed and
              its installation will be aborted with a warning message.

   4. Install the compatibility libraries (for Red Hat 8.0 only):
		# rpm -U /tmp/compat-libstdc++-7.3-2.96.zzz.i386.rpm

   5. Install the HP Server core component:
        # rpm -U /tmp/hpserver-core-5.53.xx-yy_zzz.i386.rpm

   6. Install the ITT package:
        # rpm -U /tmp/itt_lx-5.53.xx-yy_zzz.i386.rpm

   7. No system reboot is necessary.


   3.2.1.2. For Debian:

1. Download the zip file containing the appropriate HP Server Agents
       installation files for your version of Linux (the installation files
       are separated in directories named by distribution version).

2. Expand the zip file containing the HP Server Agents to a temporary
       location on your Linux system (for example /tmp)
           # unzip -o <name_of_zip_file> -d /tmp
           for example,
           # unzip -o customer.zip -d /tmp

   3. Install the MMC device driver:
           # dpkg -i -G -E /tmp/mmcdev-5.53.xx-yy_zzz.i386.deb
           NOTE: if the MMC device driver is already built in kernel or
                 installed as a kernel module, this package is not needed and
                 its installation will be aborted with a warning message.

4. Install the HP Server core component:
           # dpkg -i -G -E /tmp/hpserver-core-5.53.xx-yy_zzz.i386.deb

   5. Install the ITT package:
           # dpkg -i -G -E /tmp/itt-lx-5.53.xx-yy_zzz.i386.deb

   6. No system reboot is necessary.


3.3.  How to verify that ITT is Running

To make sure ITT is running, check the MMC device driver and ITT services.

3.3.1. Checking MMC

Type the command:

    # cat /proc/devices | grep mmcdev

    The output will be:
       - <nnn> mmcdev, if the MMC device driver is correctly installed;
       - nothing, otherwise.

Notices:
    - <nnn> is a dynamic value assigned by the operating system.
    - the MMC device driver will not be installed on Servers from
    E series (e.g., e 60, etc.) or Servers whitout a MMC/RMC card.


3.3.2. Checking ITT services

The following services must be running: hpipmsvc and webs.

Notice that in order for the GoAhead web server (webs service) to run properly
the user must configure the network correctly. For further information
about configuring the network parameters, please refer to the OS vendor
documentation.

The hpipmsvc will not run on Servers from E series (e.g., e 60, etc.) or
Servers whitout a MMC/RMC card (MMC and SEL device drivers will not be
installed).

The command to verify the status of a service is:

For Red Hat:

    # /sbin/service <service_name> status

    The output will be:
    - <service_name> (pid <process id>) is running..., if the service is
    running;

    - <service_name> is stopped, otherwise.


For SuSE:

    # /etc/init.d/<service_name> status

    The output will be:
    - Running, if the service is running;
    - Unused, otherwise.


For Turbolinux:

    # /etc/rc.d/init.d/<service_name> status

    The output will be:
    - <service_name> (pid <process id>) is running..., if the service is
    running;
    - <service_name> is stopped, otherwise.


For Caldera OpenLinux Server:

    # /etc/rc.d/init.d/<service_name> showstatus

    The output will be:
    - <service_name> is running..., if the service is running;
    - <service_name> is NOT running..., otherwise.

For Debian:

    # ps axo command | grep <service_name> | grep -v "grep"

    The output will be:
    - the service name, if the service is running;
    - nothing, otherwise.

-------------
4.  Uninstall
-------------

4.1 For distributions based on RPM (Red Hat, SuSE, TurboLinux and Caldera):

If you wish to uninstall ITT, remove the itt_lx and hpserver-core
packages by executing the following commands (you must be root):

    # rpm -e itt_lx
    # rpm -e hpserver-core

If you could NOT uninstall hpserver-core, do not proceed with the uninstall
process; see section 4.3 for more details.
If you successfully uninstalled hpserver-core, verify if the mmcdev package is
installed in your system through the command:

    # rpm -q mmcdev

If so, remove it by typing the following command:

    **PLEASE**, just do that if you are sure that the
    hpserver-core package was already UNINSTALLED !!!

    # rpm -e mmcdev

Uninstall the compatibility package (For Red Hat 8.0 only):

	# rpm -e compat-libstdc++

Notice that rpm may display warning messages about directories not empty.
You can safely disregard these messages.
Notice that hpserver-core package may be in use by other products, if so, RPM
will display a message and will not uninstall the package.
No reboot is necessary.


4.2  For Debian:

If you wish to uninstall ITT, remove the itt_lx and hpserver-core
packages by executing the following commands (you must be root):

    # dpkg -P itt_lx
    # dpkg -P hpserver-core

If you could NOT uninstall hpserver-core, do not proceed with the uninstall
process; see section 4.3 for more details.
If you successfully uninstalled hpserver-core, verify if the mmcdev package is
installed in your system through the command:

    # dpkg -s mmcdev

If so, remove it by typing the following command:

    **PLEASE**, just do that if you are sure that the
    hpserver-core package was already UNINSTALLED !!!

    # dpkg -P mmcdev


Notice that dpkg may display warning messages about directories not empty.
You can safely disregard these messages.
Notice that hpserver-core package may be in use by other products, if so, dpkg
will display a message and will not uninstall the package.
No reboot is necessary.


4.3 Important Notes

The hpserver-core package may be in use by other HP products and if so, an
error message will be displayed when you try to remove the package. The package
will remain installed in the system until all the other HP products, that
require it, be uninstalled.

The uninstall of the HP Instant Toptools does not remove the history data
files from your computer, enabling ITT to keep historic information
after a package upgrade.


---------------------------------
5.  Accessing HP Instant Toptools
---------------------------------

An administrator can view information about an HP Server by pointing a
browser to the server using the syntax:

http://servername:280

where servername represents the host name, NetBIOS name, or IP address of the
server.


--------------------
6.  Browser Settings
--------------------

Browser settings are extremely important.

   1.  Be sure to set your browser to exclude using a proxy for your
   domain/local LAN:

   On IE, be sure to check "Bypass proxy server for local addresses":
   On IE4.01 SP2: Internet Options | Connections | Advanced | Exceptions.
   On IE 5.x: Tools | Internet Options | Connections | LAN Settings | Advanced.

   On Netscape or Mozilla, be sure to enter localhost in the domains exceptions list on
   the Advanced page.
   On Netscape or Mozilla: Edit | Preferences | Advanced | Proxies | select Manual then
   View.

   2. It is also helpful to set your browser to check for newer versions of
   stored pages on every visit to the page.

   3. It is recommended that Java is enabled on your browser:
   On IE: Tools | Internet Options | Security Tab | Select Local Intranet |
   Set the "Java Permissions" status to enable On Netscape or Mozilla: Edit | Preferences
   | Advanced | Verify the "Enabled Java" box is checked


-------------------------------
7.  Resolving IP Port Conflicts
-------------------------------

HP Instant Toptools makes use of networking port number 280 for delivery of its
management content. It is possible that another software package may already be
configured to use port 280. If that package cannot be reconfigured to use a
different port number, then the Instant Toptools web server can be reconfigured
to use a different port number. Note that in so doing Toptools Device Manager
will no longer be able to detect and integrate Instant Toptools and its
information.

To resolve the port conflict, you will need to configure a new port number for
the Instant Toptools web server. Note that changing the value of other registry
entries not associated with Instant Toptools can have severe consequences, so
care should be exercised when making these modifications.

To change the port number, start the Registry Editor as follows:

   1. Stop the webs service:

   On Red Hat, Turbolinux or Caldera:

    # /etc/rc.d/init.d/webs stop

   On SuSE:

    # /etc/init.d/webs stop


   2. Using your preferred text editor, load the file '/var/hpserver/
   registry.ini'. Locate the registry key 'SOFTWARE\Hewlett-Packard\
   InstantToptools'. Under this key should exist a subkey named 'portnum'.
   Change its value to a port that does not conflict with other network
   resources (pick a value that does not causes conflict - 2345). The portnum
   string has the following format:

    portnum=c(W)PPP,

   where PPP means the port number in decimal and W the number of characters
   of PPP. For the suggested port number, the string must be:

    portnum=c(4)2345

   3. Save the modified file.

   4. Restart the webs service:

   On Red Hat, Turbo Linux or Caldera:

    # /etc/rc.d/init.d/webs start

   On SuSE:

    # /etc/init.d/webs start


The URL used to start Instant Toptools remotely must also specify the new port
number:

e.g.: http://servername:2345


---------------
8. Known Issues
---------------

8.1. General Issues:

   1. Instant Toptools has minimal support for NetRAID-4M. Instant Toptools
just acknowledges the presence of the controller but does not show further
information like physical devices attached to it and its firmware version.

   2. The Linux kernel does not support Fiber Channel. Instant Toptools does
not show any information at all about this controller and its attached devices.

   3. Information dependent on IPMI ( chassis, fan, power supply, temperature
and voltage sensors, hardware events and watchdog timer) will only be available
if the HP Server has a RMC or the MMC hardware component and the module mmcdev
is correctly loaded.

   4. An erratic behavior may happen for Servers with dual-boot (Windows
and Linux) and Instant Toptools installed on both platforms, mostly broken
links and blank pages show on the browser. This behavior is caused by the
browser trying to use a cached page from the different platform. Two settings
may contribute to this problem: the browser's local cache and a proxy server.

To correct this behavior you must clean the cache and disable the proxy server
if you have used the browser to access Instant Toptools in a platform and
intend to use the same browser to access the Instant Toptools in the other one
platform.

To clean the local cache in Internet Explorer browser:
      1. Select the Tools | Internet Options... menu item;
      2. Click the Delete Files... button;
      3. Check the Delete all offline content option;
      4. Click the OK button twice.

To disable the proxy server in Internet Explorer browser:
      1. Select the Tools | Internet Options... menu item;
      2. Select the Connections tab;
      3. Click the LAN Settings button;
      4. Uncheck the Use a proxy server option;
      5. Click the OK button twice.

   5. An erratic behavior could eventually occur for Contact and Location
values on the Identity Page. To correct this behavior proceed as described
above for dual boot systems.

   6. The help file made an NT reference... "Start ITT by clicking on
Start |Programs | HP Instant Toptools". Please, disregard this information.

   7. The following messages are displayed while stressing event generation:
   No manageable temperature sensors are installed on this system;
   No manageable voltage sensors are installed on this system;
   No manageable fan sensors are installed on this system.

   8. The status severity of the CPU fan sensor may differ from the status
severity of the event generated for this same CPU fun. When the first one has
status signed as warning, the status for its event is equal to critical.

   9. When the system is under a very high load, some information may not
be correctly shown due to timeouts.

   10. If IDE-SCSI emulation is enabled on the Linux Kernel, Configuration |
Storage Information link will show it as a SCSI controller. The type
column will be filled as "Unknown type".

   11. In Configuration Tab | Version Information, the Server image will
not be available for some recently supported Servers, e.g., LT 6000r U3.

   12. In Tools Tab | Plug-in Tools, the link to www.hp.com is wrong.

   13. Information about PCI Slots may be wrong.

   14. In Configuration Tab | Version Information, information about Agents will
only be available if the Server Agents are installed and the link
libsnmp.so.0 points to the current SNMP library installed in your system.
The link must be located at the same directory as the library and you can
discover this path by running the ldconfig program.
Example:
	# ldconfig -p | grep snmp
        libsnmp-0.4.2.so (libc6) => /usr/lib/libsnmp-0.4.2.so
    If this link does not exists, you should manually create it:
	# ln -sf /usr/lib/libsnmp-0.4.2.so /usr/lib/libsnmp.so.0
If your SNMP package relies on external cryptographic library, you will need
the link libcrypto.so to current CRYPTO library installed in your system. The
link must be located at the same directory as the library and you can discover
this path by running the ldconfig program.
Example:
	# ldconfig -p | grep libcrypto
		libcrypto.so.2 (libc6) => /lib/libcrypto.so.2
    If this link does not exists, you should manually create it:
	# ln -sf /lib/libcrypto.so /lib/libcrypto.so.2

   15. In Status Tab | Mass Storage | Physical Devices only one disk can be
located at once, using Locator LED. Otherwise, only the last LED that was turned
on will be turned off, even if HP Server is reseted. All Locator LEDs will be
turned off again only if HP Server is powered off and on.

   16. Be careful about the fact that the fields Contact/Location in page
Configuration / System Information are interpreted as HTML.

   17. depmod may display warning messages about undefined symbols on seldev
module, this message can be safely disregarded.

   18. If the HP Server tc3100 and tc4100 does not have a HP Server Remote
Management Card, the server will be treated as an E-Series server. Adding or
removing the HP Server Remote Management Card on these servers will need
it will be necessary to completely remove and install this product again.

   19. System Event Log shows some unknown events.

   20. There is no help page for some events. If you try to get help for one
of these events, it will be shown an incorrect help description.

   
8.2. Issues for Caldera 3.1 only:

	1. In Configuration Tab | Version Information | Agents, information may be
wrong.


8.3. Issues for Red Hat 8.0 only:

    1. The sysContact and sysLocation information are syncronized with SNMP. If
the SNMP daemon is not installed, ITT will record it, but you will need to set
these information again if you install the SNMP Daemon. When ITT is unable to
read these data from SNMP, the older data recorded by ITT will be reported
again.
    NOTE: Please make sure that syslocation and syscontact are not configured
        in the /etc/snmp/snmpd.conf configuration file if the SNMP daemon is
        installed.

    2. If serial number is not available by SMBIOS then it is shown as
'unknown'.

    3. For the HP Server tc3100 and tc4100 with RMC card only, unexpected
behavior were reported:
    - Sometimes information about IPMI sensors is not available. The Status
page will stop responding while the software keeps trying to get this data.
    - When many events are generated, the System Event Log may get corrupted.
ITT may report each event many times, so that the number of events reported
will be greater then the real value.
