                Hewlett-Packard TopTools Remote Control Card
     
                Firmware Version B.02.02
     
     
Connecting to the Remote Control Card requires the following minimum 
configuration:
     
        * 10BaseT compatible network or modem connection
        * Windows 95/98/NT client
        * Internet Explorer 4.01 Service Pack 1 / Netscape Navigator 4.06
     
        IMPORTANT:
        If you are a Netscape user please make sure to look at the 
        known bugs section for a list of open issues in using 
        Netscape Navigator to connect to the Remote Control Card.
______________________________________________________________________
     
CONTENTS

     
1. Instructions for addressing known issues
   1.1 Version 2.01 or greater firmware requires a serial port driver update
   1.2 LH6000 and LTr6000 graphics mode detection requires firmware update
   1.3 Downgrade of firmware will require a reset of the user database
   1.4 Some Event Log events are not decoded 
   1.5 Sometimes resizing Event Log does not work
   1.6 Sometimes scrollbar in Event Log page does not work properly 
   1.7 Sensor severity is "OK" when server power is off
   1.8 Remote Boot does not work when NetRAID is enabled 
   1.9 User and Operator Logins/Logout are not in Event Log
  1.10 Establishing a PPP connection from Windows NT takes a long time
  1.11 Resizing the browser in Netscape Navigator
  1.12 (LXR8000 ONLY) Remote Boot does not work if the Multi-Boot Support 
       option is disabled in BIOS (default)
  1.13 Disabling auto-logout timeout can prevent login from other browsers
  1.14 Microsoft IE 5.0 exhibits unexpected tab focus traversal 
  1.15 Microsoft IE 5.0 new user error text is not displayed.
  1.16 Limit use of backslashes, single quotes, and double quotes.
  1.17 Browser navigation of Group Actions not supported.
  1.18 LXR8500 sensors inaccurate or missing.
  1.19 PCI slot restrictions for LC2000 and LH3000.
     
2. Additional Hints

   2.1 What to do if all Administrator passwords are unknown or lost
   2.2 Changing PPP parameters does not take effect immediately 
   2.3 Gracefully Shutdown Operating System
   2.4 Auto-Logout (5 minutes)
   2.5 Updating card firmware if red LED is flashing (firmware corrupted)
   2.6 Update the NetServer agents to version 4.50/4.51 or higher.
   2.7 Recovering from incorrect memory size discovery.     
   2.8 Group Actions capabilities and limitations
_______________________________________________________________________
     
     
1. Instructions for addressing known issues

1.1 Version 2.01 or greater firmware requires a serial port driver update

  For NT systems, you will need to install the new serial port driver
  prior to upgrading the card's firmware.  Failure to follow this order
  will result in an NT blue screen indicating an NMI occurred.  To
  recover you need to pull out the TopTools Remote Control card and
  upgrade the serial port driver or at least uninstall the previous
  driver.  This driver is named "HP TopTools Remote Control" in the
  "Add/Remove Programs" section of the Control Panel.

1.2 LH6000 and LTr6000 graphics mode detection requires firmware update

  For the LH6000 and LTr6000 with a TopTools Remote Control Card, updated
  TopTools Remote Control Card firmware and NetServer BIOS must be retrieved
  from the HP web site.  This is to correct a problem where the text console
  redirection feature is unable to detect that the server is in a graphics
  display mode.  Unless the firmware is updated the text panel will display
  random text rather than a message indicating the server is in graphics mode.

  The Remote Control Card firmware version with this fix is B.02.02, while the
  associated BIOS version is 4.06.22 or greater.  Both of these files can be
  retrieved via FTP starting from ftp://ftp.hp.com/pub/servers/software.
  The filenames are "ttrc0202.exe" and either "lh6kbios.exe" or "lt6kbios.exe"
  depending on your system model.

1.3 Downgrade of firmware will require a reset of the user database

  There was a change in storage format of the user password between
  major versions B.01.xx and B.02.xx.  This change is handled by the
  card when upgrading from the older firmware, but after a downgrade you
  will need to reset the user database since the saved data won't allow
  reconstruction of the prior passwords.

1.4 Event Log events are not decoded
     
  NIC and Volume Capacity events generated by the NetServer Agents are 
  not decoded correctly in the Remote Control Card Event Log.
     
  Workaround:
     
        The events can be viewed correctly through the TopTools 
        for Servers Event Log.
     
  FIX:	Upgrade to the NetServer Agents on the HP NetServer
	Navigator CD version L.13.00 or greater.
     
1.5 Sometimes resizing the Event Log does not work
     
  It is possible to resize the Event Log window to show a greater number of
  events; sometimes the "End of Log" message appears prematurely.
     
  Workaround:
     
        Repeat the resize until it works, press the Event Log button again 
        to set size back to default.
     
1.6 Sometimes scrollbar in Event Log page does not work properly.
     
  The scrollbar sometimes will not allow scrolling of the events.
     
   Workaround:
     
        Refresh the Event Log applet by clicking to another tab, and then 
        going back to the status tab.
     
1.7 Sensor severity is "OK" even when the server power is off
     
  The sensors will show the last known reading of the sensors before the 
  server was powered off.  The power state of the server is indicated by
  the green circle in the upper left corner of the screen.  If the 
  green circle is present the server is ON, if it is not present, the
  server is OFF.
     
1.8 Remote Boot does not work (NetRAID enabled in system)
     
  Remote floppy boot fails if embedded NetRAID (LH3) is enabled or a 
  NetRAID card is in a PCI slot number higher than the Remote Control Card.
     
  Workaround:
     
        Embedded NetRAID - disable by entering BIOS setup menu before 
	executing remote boot; enable again after loading image.
     
        NetRAID card - swap Remote Control Card and NetRAID PCI card slots
     
  FIX: Upgrade to the latest NetRAID BIOS version, MUST be greater than
       B.01.03.
     
1.9 User and Operator Logins/Logout are not in Event Log 
     
  Only Administrator Login/Logouts are currently logged to the Event Log.

1.10 Establishing a PPP connection from Windows NT takes a long time

  Using NT Dial-up Networking to connect to the Remote Control Card results
  in a delay of up to 30 seconds.  The delay occurs while Dial-up Networking 
  reports "Registering your computer on the remote network...".  On a slow 
  modem link, Dial-up Networking may timeout before completing the PPP 
  connection. 

  Workaround:
	
	Use Windows 95 Dial-up Networking.

1.11 Resizing the browser in Netscape Navigator

  ANY resize of the browser will result in a logout and is NOT supported.

  Workaround:

	Size the browser as desired before connecting to the Card.

1.12 (LXR8000 ONLY) Remote Boot does not work if the Multi-Boot Support 
     option is disabled (default).

  The Remote Boot feature will not work if the Multi-Boot Support option is 
  disabled.  The default for this option is disabled, so it must be changed 
  manually by user.

  Workaround:

	Enter BIOS setup by pressing <F2> during the system boot.  Select 
	the Advanced Menu and then select the Advanced Chipset Control 
	Sub-Menu.  Enable the Multi-Boot Support option.

1.13 Disabling auto-logout timeout can prevent login from other browsers

  For the B.02.xx level firmware there is an auto-logout feature that
  can be set by an administrator to log off a user after several minutes
  of inactivity.  If this timer is disabled, a browser that is logged
  on to the card must be logged off manually or else a different browser
  will be unable to log on.

1.14 Microsoft IE 5.0 exhibits unexpected tab focus traversal

  Various pages and dialog boxes will not function as expected using
  keyboard navigation under Internet Explorer 5.0.  One notable instance
  of this is the Login dialog where rather than moving to the password
  entry field a tab will place input focus on the browser's navigation
  entry field.  A workaround is to use the mouse to select input fields
  and to press buttons.

1.15 Microsoft IE 5.0 new user error text is not displayed.

  The new user dialog box should display error text indicating that
  either the password and it's confirmation are different or that the
  chosen password is too short under these conditions, but this text is
  not displayed under Internet Explorer 5.0 with the shipping Java
  Virtual Machine.  The fix is to download and install a newer JVM from
  the Microsoft web site.

1.16 Limit use of backslashes, single quotes, and double quotes.

  There are several places where text strings are accepted as input for
  both the onboard UI and the group actions.  Unless absolutely
  necessary you should limit use of the characters indicated to minimize
  side-effects or problems with parsing of this text.  As an example, do
  not use any of these characters in the Add User fields because the
  name will not be stored verbatim but will be mangled to be unusable.

1.17 Browser navigation of Group Actions not supported

  The paradigm used by the group actions is not compatible with the
  browser's forward and back buttons -- in fact most browser navigation
  will not work as they would for regular HTML pages.  The screens
  progress forward only and browser based navigation will prevent them from
  functioning properly.

1.18 Some LXR8500 sensors may be inaccurate or missing.

  Due to various changes to support IPMI 1.0 as well as IPMI 0.9, some
  items on the sensor page may be erroneous.  As an example the number
  of CPU's may be inaccurately reported, or the sense of the logic of
  the chassis intrusion sensor may be backward.  As a workaround, an
  event is always generated and displayable via the event log in cases
  where there are true problems with the NetServer, and so this should
  be used as the primary source of server state information.

1.19 PCI slot restrictions for LC2000 and LH3000.

  Due to the design of the PCI subsystem, the TopTools Remote Control
  Card must be placed in a specific PCI bus for an LC2000 and LH3000.
  For the LC2000 these are slots 1 and 2, while for an LH3000 these are
  slots 7 and 8.  Failure to comply with these restrictions will not
  allow the card to perform keyboard redirection as expected.

2. Additional Hints

2.1 All Administrator passwords are unknown or lost

  Try the default username (ADMIN) and password (ADMIN).  If this
  doesn't work, run the User Database Reset utility shipped on the
  NetServer Navigator CD.  This utility can be found in the NetServer
  Utilities section and will erase all user information, then generate
  the default username/password account.
 
2.2 Changing PPP parameters does not take effect immediately 

  The new PPP parameters are normally set after a PPP session has completed.
  To force changes to take effect via a LAN connection, disable PPP, click
  "Apply", then re-enable PPP and click "Apply" again.

2.3 Gracefully Shutdown Operating System

  By default all power control commands are done gracefully, but a graceful 
  shutdown of the server will not occur if the graceful shutdown agent
  is not installed in the operating system.  The agents are only supported on 
  Windows NT, Netware, and SCO.  For other operating systems, use text console
  redirection to manually shut down before resetting or powering off
  the server.

2.4 Auto-Logout (default 5 minutes)

  The card will automatically logout users after an inactivity period of 
  five minutes.  During a firmware update over modem a connection the 
  auto-logout feature will not take effect.  The Auto-Logout timeout 
  can be changed via the card configuration screen by an ADMINISTRATOR
  priveleged user.

2.5 Updating card firmware if red LED is flashing (firmware corrupted)

  If the red LED is flashing in the firmware corrupted pattern, a new 
  image can be downloaded to the card via a the Remote Control Card's 
  serial port.  

  Using a Null Modem cable connected to the Remote Control Card serial port
  open a HyperTerminal session with baud rate set to 38400.  Flow control
  should be set to Hardware.  Select "Send File" from the  Transfer Menu and 
  set the protocol to 1K Xmodem and specify the file name.  The firmware
  image file has a ".bin" extension and is located under the /ttrc/us 
  directory on the HP NetServer Navigator CD version L.13.00 or greater.

2.6 Update the NetServer agents to version 4.50/4.51 or higher.

  The latest versions of the agents incorporate various changes which
  provide better integration of the new TopTools Remote Control cards'
  group actions into the TopTools Management Server.  As an example,
  changing the IP address of the Remote Control Card will be noticed by
  the agents and will be reflected after the next discovery.  Without
  this fix the Management Server would indicate there are two Remote
  Control cards in a particular server, and trial and error would be
  necessary to find out which is the correct entry.

2.7 Recovering from incorrect memory size discovery.

  The B.01.09 and earlier firmware would incorrectly handle certain
  memory configurations.  If you believe that the memory reported is
  incorrect, update the TopTools Remote Control Card's firmware to
  B.02.02 if you haven't done so already, then reboot the NetServer.
  This will allow the card to reinitialize its database.

2.8 Group Actions capabilities and limitations

  The TopTools 4.5 software enhance the functionality of the TopTools
  Remote Control Card by allowing several cards to be updated/modified
  at once.  You can perform the following actions:

  Card Group Actions:
  - add user
  - delete user
  - change user password
  - view configured users
  - upate card firmware

  Server Group Actions:
  - power on/off

  Each group action requires a login username and password.  For
  security purposes you must login before executing each group action.
  Each group action must be launched from the TopTools Device Manager
  through the Action Menu.  The browser's BACK button cannot be used to
  execute consecutive group actions.

  To login to multiple cards, you must have an account with the same
  username and password on each card.  In addition, your user account
  must have administrator privileges in order to perform group actions.
