-----------------------------------------------------------------------------

               H E W L E T T  P A C K A R D  C O M P A N Y

         HP ProLiant Support Pack (PSP) for Novell NetWare Help

                              Version 6.10a

-----------------------------------------------------------------------------
1. What is a ProLiant Support Pack (PSP)
2. Minimum OS Requirements for the PSP
3. NetWare Red-box Installation
4. Contents of PSP v6.10a
   4.1 NetWare PSP
   4.2 New features included in this PSP
   4.3 New and updated drivers/components in this PSP
   4.4 Drivers removed from this PSP
5. Software Installation
   5.1 Command Line Deployment Using CPQDPLOY.NLM
   5.2 Graphical (NUT-based) Deployment using CPQDPLOY.NLM
   5.3 Command-Line by Individual Package
   5.4 Graphical (NUT-based) Deployment by Individual Package
   5.5 List of Command-line parameters
   5.6 Installation Examples
5. Log files
6. FAQ

-----------------------------------------------------------------------------
1. What is a ProLiant Support Paq (PSP)

A ProLiant Support Paq (PSP) is a bundle of software packages.  Each package
contains an individual driver, utility, or agent software which comes
self-contained with all of the necessary support software for that package.
As an example, the  storage driver package containing CPQSCSI.HAM will
have the associated Novell and HP files, such as NWPA.NLM and
CPQSHD.CDM, that were used during HP's rigorous software testing
included in the package.  Each package contains an NLM extraction utility
to unpack the compressed package contents.

CPQDPLOY.NLM is provided as a package manager for installation of multiple
packages, either through command-line or a NUT-based interface.
CPQDPLOY.NLM uses a bundle XML definition file in the format (BP000xxx.XML)
to determine what packages belong in a bundle, which operating systems are
supported, and other relevant information.

Each package is also installable individually through either its own
command-line or NUT-based interface.  Each individual package has a unique
package number assigned to it by HP.  The packages will always have the
format CP0xxxxx.NLM.

*NOTE: The PSP is HP's replacement for the now withdrawn
       CPQNSSU (NSSD) utility.

*NOTE: The ProLiant Support Pack (PSP) is the HP rebranded name for the
       former Compaq Support Paq (CSP)

The purpose of a PSP is to provide customers with the latest software,
utilities, and drivers for HP Proliant servers. 

 
2 Minimum OS Requirements for the PSP

The PSP currently is shipped as a single bundle that provides support
for NetWare v5.1, and NetWare v6.0.  The PSP expects that you have at a
minimum the following requirements:

   NetWare v4.2    Not Supported
   NetWare v5.1    Base installation.  However, Support Pack 5 or later
                   is recommended.
   NetWare v6.0    Base installation.  However, Support Pack 2 or later
                   is recommended.

*NOTE: NetWare v4.2 is no longer supported as of v6.00.  The last version of
       the CSP for NetWare v4.2 is available on the NetWare v4.2 driver page
       on www.compaq.com/support/files

*NOTE: Small Business versions of the above versions of NetWare are also
       supported.

The PSP is intended to be used after OS installation to update drivers
and install HP-specific utilities (such as Power Management, Health,
etc), agents (Foundation, Server, LAN, and Storage), and Compaq Survey.


3 NetWare Red-box installation

While the PSP cannot be used during initial NetWare red-box installation,
HP does provide the necessary drivers for red-box installation on the
Smart Start CD in the \COMPAQ\DRIVERS\(OS version) subdirectory in flat
file format.

Support for red-box installations can be accomplished by copying the
contents of the above directory off the Smart Start CD into the
C:\NWUPDATE directory on the server after the hard drive has had a DOS
partition defined and formatted, but prior to NetWare's driver detection.

After the installation has completed, use the PSP as described in
Section 5 to 'complete the server'.

                      
4. Contents of PSP v6.10a

4.1 NetWare PSP

*Note: These are listed in component number order.  Because of load
       dependencies, this is not the order in which drivers are installed
       by the HP Deployment Utility.

  Files Included  OS Suptd               Description
  ==============  ========   ================================================
   CPQDPLOY.NLM   51/60      HP ProLiant Deployment Utility v6.10a
   BP000120.XML   51/60      Bundle installation XML file for CPQDPLOY.NLM
   CPQCSP.TXT                This file
   CP002607.NLM   51         Supports the Compaq Array adapters for NetWare
                               v4.2 and 5.1 (CPQARRAY.HAM)
   CP002608.NLM   60         Supports the Compaq Array adapters for NetWare
                               v6.0 (CPQARRAY.HAM)
   CP002609.NLM   51/60      Supports the Compaq SCSI adapters (CPQSCSI.HAM)
   CP002610.NLM   51/60      Supports the Compaq 64-Bit/66MHz Wide Ultra3
                               Controller (ADPT160M.HAM)
   CP002611.NLM   51/60      Supports the Compaq Fibre Channel Adapters
                               (CPQFC.HAM)
   CP002612.NLM   51/60      Supports the Compaq NetFlex-3 Ethernet Adapters
                               (CPQNF3.LAN)
   CP002613.NLM   51/60      Supports the Compaq N100 Fast-Ethernet Adapters
                               (N100.LAN)
   CP002614.NLM   51/60      Supports the Compaq N1000 Gigabit Ethernet
                               Adapters (N1000.LAN)
   CP002615.NLM   51/60      Provides the Compaq NC67xx/NC77xx Gigabit
                               Ethernet NIC Driver (Q57.LAN)
   CP002616.NLM   51/60      Provides the Compaq NC67xx/NC77xx Gigabit
                               Ethernet NIC Teaming Driver (QASP.LAN)
   CP002617.NLM   51/60      Supports the SysKonnect FDDI Adapters
                               (SKFPNW.LAN)
   CP002618.NLM   60         Provides the hp ProLiant ACPI Platform Support
                               Module for NetWare v6.x (CPQACPI.PSM)
   CP002619.NLM   51/60      Provides the Compaq Multi-Processor Driver
                               (CPQMPK.PSM)
   CP002620.NLM   51/60      Provides the hp ProLiant Server Health Driver
                                Tier 1 (CPQHLTH.NLM)
   CP002621.NLM   51/60      Provides the Enhanced Integrated Management
                                Utility (CPQEIMD.NLM)
   CP002622.NLM   51/60      Supports the Compaq Remote Insight Adapter
                               (CPQRI.NLM)
   CP002623.NLM   51/60      Provides the hp ProLiant iLo Management Interface
                               Driver (CPQCI.NLM)
   CP002624.NLM   51/60      Provides the Smart Array Online Configuration
                               Utility (CPQONLIN.NLM)
   CP002625.NLM   51/60      Provides the Compaq Integrated Management Log
                               Viewer (CPQIML.NLM)
   CP002626.NLM   51         Provides the AMI IDE/ATA/ATAPI UDMA Host Adapter
                               Module (MEGAIDE.HAM)
   CP002627.NLM   60         Provides the NetWare NWPA MegaRIDE HAM Driver
                               for NetWare v6.0 (MEGARIDE.HAM)
   CP002628.NLM   51         Provides the NetWare NWPA MegaRIDE HAM Driver
                               for NetWare v5.1 (MEGARIDE.HAM)
   CP002629.NLM   51/60      Provides the Integrated ATA RAID Management
                               Utility (SPY.NLM)
   CP002630.NLM   51/60      Provides the hp ProLiant System Bus Driver
                               (Hot-Plug PCI) Support (CPQSBD.NLM)
   CP002631.NLM   51/60      Provides the Compaq Power Subsystem Utility                               (CPQPOWER.NLM)
   CP002632.NLM   51/60      Supports the Compaq Unified RAID driver (CPQRAID.HAM)
   CP002633.NLM   51/60      Provides the Compaq Foundation Agent
                              (CPQHOST.NLM)
   CP002634.NLM   51/60      Provides the Compaq Server Agent (CPQBSSA.NLM)
   CP002635.NLM   51/60      Provides the Compaq NIC Agent (CPQNCSA.NLM)
   CP002636.NLM   51/60      Provides the Compaq Storage Agent (CQMGSTOR.NLM)
   CP002637.NLM   51/60      Provides the Compaq Survey Utility (SURVEY.NLM)


51 = NetWare v5.1, NetWare v5.1 w/SP4, NetWare v5.1 w/SP5
60 = NetWare v6.0, NetWare v6.0 w/SP1, NetWare v6.0 w/SP2


4.2 New features included in this PSP

In this version of the PSP, minor bug fixes have been made.  The capability
to detect and correctly install the IMD Utility only on servers with this
feature has been added.


4.3 New and updated drivers/components in this PSP

  o Support for the following adapters and utilities has been updated:
           
      > Compaq Array adapters for NetWare v5.1
         CP002607.NLM
           (CPQARRAY.HAM) no change
           (CPQSHD.CDM) from v1.54 to v1.56

      > Compaq Array adapters for NetWare v6.0
         CP002608.NLM
           (CPQARRAY.HAM) from v2.14 to v2.16
           (CPQSHD.CDM) from v1.54 to v1.56

      > Compaq SCSI adapters
         CP002609.NLM
           (CPQSCSI.HAM) no changes
           (CPQSHD.CDM) from v1.54 to v1.56

      > Compaq 64-Bit/66MHz Wide Ultra3 Controller Driver
         CP002610.NLM
           (ADPT160M.HAM) from v17.12m to v18.20m
           (CPQSHD.CDM) from v1.54 to v1.56

      > Compaq Fibre Channel Adapters
         CP002611.NLM
           (CPQFC.HAM) no changes          
           (CPQSHD.CDM) from v1.54 to v1.56

      > hp ProLiant ACPI Platform Support Module
         CP002618.NLM
          (CPQACPI.PSM) from v1.03 to v1.04

      > hp ProLiant Server Health Driver Tier 1
         CP002620.NLM
          (CPQHLTH.NLM) from v5.04 to v5.05

      > Smart Array Online Configuration Utility
         CP002624.NLM
          (CPQONLIN.NLM) from v2.65b to v2.66a

      > Integrated ATA RAID Management Utility
         CP002629.NLM
          (SPY.NLM) from v4.05 to v4.08

      > hp ProLiant System Bus Driver (Hot-Plug PCI) Support
         CP002630.NLM
          (CPQSBD.NLM) from v3.15 to v3.16

      > Compaq Power Subsystem Utility
         CP002631.NLM
          (CPQPOWER.NLM) from v1.11 to v1.12

      > Compaq Unified RAID driver
         CP002632.NLM
          (CPQRAID.HAM) from v2.04 to v2.05

      > Compaq Management Agents
         CP002633.NLM, CP002634.NLM, CP002635.NLM, CP002636.NLM
          from v6.00 to v6.10

      > Compaq Survey Utility
         CP002637.NLM
          from v2.46 to v2.48



4.4 Drivers removed from this PSP

  o Support for the following adapters and utilities has been removed
    because the equivalent drivers are available on the Novell base media:

    None



5. Software Installation

The PSP can be installed in one of four ways: 

  o  Command-line by CPQDPLOY.NLM (See Section 5.1)

  o  Graphical (NUT-based) by CPQDPLOY.NLM (See Section 5.2)

  o  Command-line by individual package (See Section 5.3)

  o  Graphical (NUT-based) by individual package (See Section 5.4)


5.1 Command Line Deployment Using CPQDPLOY.NLM

Command-line installation using CPQDPLOY.NLM is achieved by passing as
arguments either a bundle file name or component file name to install
along with either the /nui or /s switches.  A bundle file name is of the
format BP00XXXX.XML.  A component file name is of the format CP0XXXXX.NLM.
CPQDPLOY.NLM is capable of installing either one bundle or component at a
time.  A bundle is a HP-tested collection of component packages which
will deploy device drivers, utilities, agents, or Survey.  See Section 5.6
for information on how to start the deployment utility with the "no user
interface" option.  If you do not provide the name of a bundle or component
package to install and use the -nui or -s option, the installation will
fail.  Regardless of the command-line option passed, information about the
success/failure of the installation is logged in the SYS:\ETC\CPQLOG.LOG
file.


5.2 Graphical (NUT-based) Deployment using CPQDPLOY.NLM

Graphical installation using CPQDPLOY.NLM can be done by not using the
-s or -nui parameters to CPQDPLOY.NLM.  You may optionally pass the name
of the bundle or component that you want installed.  The deployment selection
screen will show you the currently installed version of the software on your
server (if found), the version that the component package will install, and
a description of the component package.  The following keystrokes are
available on the graphical screen:

F1 = Display Help
F2 = Toggles the force option
F3 = Toggles the reboot option
F4 = Marks/Unmarks all the components in the list
F5 = Marks/Unmarks an individual component or category in the list
F7 = Toggles whether the STARTUP.NCF and AUTOEXEC.NCF files should be modified
F8 = Display more options
F10 = Installs the marked packages
Enter = Shows the component package details and payload information
Esc = Return to the previous screen or exit the deployment utility

Once installation has completed, a component installation status screen will
be displayed showing the results of the installation.  From this screen,
you can press F3 to view the SYS:\ETC\CPQLOG.LOG file or press Enter on a
component to see further details of the installation.  Pressing Escape
terminates the component installer.


5.3 Command-Line by Individual Package

Command-line installation of an individual component can be done by
typing the name of the component package (ie CP002620) preceded by the
optional LOAD command and either the /nui or /s switches.  An individual
component package file name is of the format CP0XXXXX.NLM.  The individual
component installer is capable of installing a single component at a time.
A component package will deploy device drivers, utilities, agents, or
Survey.  See Section 5.6 for information on how to start the individual
component installer with the "no user interface" option.  Regardless of
the command-line option passed, information about the success/failure of
the installation is logged in the SYS:\ETC\CPQLOG.LOG file.

5.4 Graphical (NUT-based) Deployment by Individual Package

Graphical installation using the individual component installer can be
done by not using the -s or -nui parameters to the component package.
The deployment selection screen will show you the currently installed
version of the component package on your server (if found), the version
that the component package will install, and a description of the
component package.  The following keystrokes are available on the
graphical screen:

F1 = Display Help
F2 = Toggles the force option
F3 = Toggles the reboot option
F4 = Marks/Unmarks the component to be installed
F5 = Marks/Unmarks the component to be installed
F7 = Toggles whether the STARTUP.NCF and AUTOEXEC.NCF files should be modified 
F8 = Display more options
F10 = Installs the marked package
Enter = Shows the component package details and payload information
Esc = Return to the previous screen or exit the deployment utility

Once installation has completed, a component installation status screen will
be displayed showing the results of the installation.  From this screen,
you can press F3 to view the SYS:\ETC\CPQLOG.LOG file or press Enter on the
component to see further details of the installation.  Pressing Escape
terminates the component installer.

5.5 List of Command-line parameters

NOTE: Parameters can be entered as upper or lower case, with either a
      slash '/' or dash '-' preceding them.  Parameters in parentheses can
      be used in place of the whole word (ie -(h)elp means that either -h,
      -help, /h or /help can be used)

CPQDPLOY command-line parameters:

   <VOLUME:\PATH\>CPQDPLOY [/H[ELP]|/?] [/NUI] [/S[ILENT]] [/R[EBOOT]]
                           [/F[ORCE]] [/NOMODS] 
                           [BP000xxx.XML|CP00xxxx.NLM]

   <VOLUME:\PATH\>CPQDPLOY [-H[ELP]|-?] [-NUI] [-S[ILENT]] [-R[EBOOT]]
                           [-F[ORCE]] [-NOMODS]  
                           [BP000xxx.XML|CP00xxxx.NLM]

    -(h)elp         Show this list of command-line parameters
    -(r)eboot       Reboot if a package installed requires it and no
                    failures occurred
    -(s)ilent       Silent installation means that all messages will be
                    logged to the SYS:\ETC\CPQLOG.LOG file.  No console
                    output or GUI will be shown.
    -(nui)          No user interface will be displayed.  However, during
                    installation, output will be shown at the system
                    console unless the -(s)ilent option is also used.
    -(f)orce        Force the installation of a package, regardless of
                    software version installed on the server as long as
                    the prerequisite software requirements have been met.
    -nomods	    Made no modifications to the STARTUP.NCF and
 		    AUTOEXEC.NCF files.  The default option (without this
                    parameter) is to make all modifications as needed
		    during the installation of each component package.


Individual Component command-line parameters:

   <VOLUME:\PATH\>CP00XXXX [/H[ELP]|/?] [/NUI] [/S[ILENT]] [/NOMODS]
                           [/F[ORCE]] [/I] [/G] [/R[EBOOT]] [/xVOL:\PATH]

   <VOLUME:\PATH\>CP00XXXX [-H[ELP]|-?] [-NUI] [-S[ILENT]] [-NOMODS]
                           [-F[ORCE]] [-I] [-G] [-R[EBOOT]] [-xVOL:\PATH]

    -(h)elp         Show this list of command-line parameters
    -(r)eboot       Reboot if a package installed requires it and no
                    failures occurred
    -(s)ilent       Silent installation means that all messages will be
                    logged to the SYS:\ETC\CPQLOG.LOG file.  No console
                    output or GUI will be shown.
    -(nui)          No user interface will be displayed.  However, during
                    installation, output will be shown at the system
                    console unless the -(s)ilent option is also used.
    -(f)orce        Force the installation of a package, regardless of
                    software version installed on the server as long as
                    the prerequisite software requirements have been met.
    -i              Display the Package Payload information (no
                    installation occurs)
    -g              Display Package Source and Destination information (no
                    installation occurs)
    -xVol:\Path     Extract the contents of the package to the directory
                    pointed to by Vol:\Path.  Note that there is no space
                    between the x and the path.  If VOL:\Path does not
                    exist, an attempt is made to create the Path.  An
                    invalid volume and/or path will be ignored and the
                    extraction terminated.
    -nomods	    Made no modifications to the STARTUP.NCF and
 		    AUTOEXEC.NCF files.  The default option (without this
                    parameter) is to make all modifications as needed
		    during the installation of each component package.



5.6 Installation Examples

o Normal program execution to deploy a bundle of components for NetWare v5.1.
  The deployment utility will expect the bundle file and all bundles to be
  in the directory which it was called from.  If a bundle file is not found,
  you will be prompted for the path to a bundle file.

  SYS:\DEPLOY\CPQDPLOY

o Using CPQDPLOY to deploy a bundle

  LOAD SYS:\DEPLOY\CPQDPLOY BP000120.XML

o Using the force option for CPQDPLOY.NLM

  LOAD SYS:\DEPLOY\CPQDPLOY -f

o Using the "no user interface" option (No GUI)

  LOAD SYS:\DEPLOY\CPQDPLOY -nui

o Using the silent option (no command-line or GUI output)

  LOAD SYS:\DEPLOY\CPQDPLOY -s

o Using the silent option and the force option

  LOAD SYS:\DEPLOY\CPQDLOY -s -f

o Installing a single component with GUI

  LOAD SYS:\DEPLOY\CP002618

o Installing a single component with force and "no user interface" options

  LOAD SYS:\DEPLOY\CP002628 -f -nui

o Extracting a components contents to another directory

  LOAD SYS:\DEPLOY\CP002609 -xSYS:\TEMP

o Install the contents of a package after extracting a components contents
  to another directory

  LOAD SYS:\TEMP\CPQSETUP

o Determining a components contents without extracting

  LOAD SYS:\DEPLOY\CP002631 -i

o Determining the source directory, destination directory and primary NLM
  that will be installed by the component package

  LOAD SYS:\DEPLOY\CP002621 -g

o Deploying a single component from the deployment utility with force option

  LOAD SYS:\DEPLOY\CPQDPLOY CP002625.NLM -f



6. Log files

During PSP installation an installation log file is generated that contains
more detailed information about the installation than is displayed by
the CPQDPLOY.NLM deployment manager status screen.  The log file is useful
in determining why a particular component failed to install properly.
Each component writes to the installation log file that resides at the
following location:

                 SYS:\ETC\CPQLOG.LOG

To view the installation log file from within the CPQDPLOY.NLM Installation
Status screen, press the F3 key.

To clear the installation log file while it is displayed in the CPQDPLOY.NLM
Installation Status screen, press the F2 key.

The installation log file can also be displayed using any text editor.



7. FAQ

Issue:      I used the /r flag to reboot the server, one of the packages
            installed required a reboot, but the server did not reboot.  What
            is happening?
Resolution: If any of the packages chosen for installation fails the
            installation, a reboot will not occur.  This is so the
            administrator can examine a server to determine and resolve a
            software installation failure before activating any changes.

Issue:      When I examine the package contents, the version of the driver
            in the package is newer than what I have on my server.  However,
            one of the support files is older than the version that is
            contained in the package.  What happens during installation?
Resolution: Each file within a package is version checked (and date checked
            for non-NLM files) before the file is installed on the server.
            If one file in the package is newer than the file on the
            server, then the version in the package will be installed.  If
            another file in the package is older than the version on the
            server, then the version that is currently on the server will
            be retained.
*NOTE:      If the /force flag is used, then no version checking is done.
            All files in the package will be installed even if one of
            the files on the server is newer than the one in the package.
            However, OS dependencies are maintained.  For instance, the
            CPQACPI.PSM, which is only supported on NetWare v6.0, will not
            be installed on a server running NetWare v5.1, even if
            the /force flag is used.

Issue:      When I install a driver, then run the installation utility a
            second time before rebooting the server, the version shown in
            the installation utility does not match the version loaded
            via the MODULES console command.
Resolution: Once an installation has occurred, the installation utility
            will check against the installed version on the fixed disk.
            Even if the version loaded is different, the version compared
            against for installations is the version on the physical media.

Issue:      When I do a command-line install and pass the /r parameter, the
            server does not reboot.
Resolution: Normally this occurs because either the version of the software
            to be installed is the same or older than the version installed
            on the server or a failure occurred during the installation
            (such as a prerequisite was not met).  Check the 
            SYS:\ETC\CPQLOG.LOG file to determine the cause of the failure.

Issue:      When I choose the force installation, some packages are not
            installed.
Resolution: The force option will only cause packages to install when
            the software prerequisites for the package have been met.
            If the software prerequisites for a package have not been met,
            the package installation will fail.  In a future release of
            the PSP, an option will be provided to allow installation even
            if the software prerequisites that a package requires are not
            met.

Issue:      During installation, I get error messages about unable to read
            xxx from an XML file or an Error 10010 ... message.
Resolution: As above, this is normally caused by a corrupted package, which
            normally occurs during download.  If a package XML file cannot
            be parsed correctly, the installation of that package will
            terminate with an error such as the above.  To resolve this
            issue, try downloading the package again from
            http://www.compaq.com.

Issue:      When I try to install the PSP, I get the message "The software
            in this package is not intended for this version of NetWare."
Resolution: There are two causes of this.  First, if you have placed both
            versions of the PSP in the same directory, the Bundle XML file
            (BP00xxxx.XML) selected could be for another version of NetWare.
            Second, the package you have chosen to install is not intended
            for the version of NetWare that is currently installed on the
            server.

Issue:      When I start the PSP with CPQDPLOY.NLM, I get a prompt asking
            me to 'Enter a path to a supported bundle XML file'.
Resolution: This is caused by having CPQDPLOY.NLM in a directory without
            a valid bundle file.  A valid bundle file is a bundle file
            of the format BP000xxx.XML and which is supported by the currently
            installed version of NetWare.  CPQDPLOY.NLM may be in a
            directory with a bundle file, but if the bundle file does not
            provide support for the currently installed version of NetWare,
            you will be prompted to enter a path to a valid bundle file.
            You can press F1 to see an example of a valid path.

Issue:      When upgrading from NetWare v5.x to NetWare v6.0, I get
            an error message during the start of the installation where
            NWPA.NLM is reporting symbols missing for kResume and kSuspend.
Resolution: This is caused by an older version of NWPA.NLM being left in
            the C:\NWUPDATE directory from a previous installation.  The
            above symbols were removed from the kernel in NetWare v6.0.
            To resolve the issue, remove the older NWPA.NLM from the
            C:\NWUPDATE directory.


-----------------------------------------------------------------------------

Copyright 2000-2002 Compaq Information Technologies Group, L.P.

All other product names mentioned herein may be trademarks and/or registered
trademarks of their respective companies.

Compaq shall not be liable for technical or editorial errors or
omissions contained herein. The information in this document is provided
"as is" without warranty of any kind and is subject to change without
notice. The warranties for Compaq products are set forth in the express
limited warranty statements accompanying such products. Nothing herein
should be construed as constituting an additional warranty.
