----------------------------------------------------------------------------- C O M P A Q C O M P U T E R C O R P O R A T I O N Compaq Support Paq for Novell NetWare Help Version 1.04a ----------------------------------------------------------------------------- 1. What is a Compaq Support Paq (CSP) 2. Minimum Requirements for the CSP 2.1 Minimum OS Requirements for the CSP 2.2 NetWare Red-box Installation 3. Contents of CSP v1.04a 3.1 NetWare v5.1 CSP 3.2 NetWare v4.2 CSP 4. Software Installation 4.1 Command Line Deployment Using CPQDPLOY.NLM 4.2 Graphical (NUT-based) Deployment using CPQDPLOY.NLM 4.3 Command-Line by Individual Package 4.4 Graphical (NUT-based) Deployment by Individual Package 4.5 CPQSETUP.NLM (Individual Component Installer) after Component Extraction 4.6 List of Command-line parameters 4.7 Installation Examples 5. Log files 6. Troubleshooting CSP installations 7. Additional Information ----------------------------------------------------------------------------- 1. What is a Compaq Support Paq (CSP) A Compaq Support Paq (CSP) 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 Compaq NWPA files, such as NWPA.NLM and CPQSHD.CDM, that were used during Compaq'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 Compaq. The packages will always have the format CP0xxxxx.NLM. *NOTE: The CSP is Compaq's replacement for the soon-to-be withdrawn CPSNSSU (NSSD) utility. The purpose of a CSP is to provide you with the latest software, utilities, and drivers for Compaq Proliant servers. 2 Minimum Requirements for the CSP 2.1 Minimum OS Requirements for the CSP The CSP currently is shipped in separate bundles for NetWare v4.2 and NetWare v5.1. Each bundle will only run on the version of NetWare it supports. The CSP expects that you have at a minimum the following requirements: NetWare v4.2 Base installation plus the CLIBAUX1.EXE (CLIBAUX.NLM) patch which is available at http://support.novell.com. Support Pack 9 contains the above NLM and is the recommended minimum support pack level. NetWare v5.1 Base installation. However, Support Pack 2a or later is recommended. NetWare v6.0 Will be supported in a future CSP *NOTE: Failure to obtain the CLIBAUX1.EXE patch will cause the NetWare v4.2 CSP deployment to fail with an unresolved external "_closedir_510". *NOTE: Small Business versions of the above versions of NetWare are also supported. The CSP is intended to be used after OS installation to update drivers and install Compaq-specific utilities (such as Power Management, Health, etc), agents (Foundation, Server, LAN, and Storage), and Compaq Survey. 2.2 NetWare Red-box installation While the CSP cannot be used during initial NetWare red-box installation, Compaq does provide the necessary drivers for red-box installation on the Smart Start CD in the \CPQSUPSW\NSSD directory 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 CSP as described in Section 4 to 'complete the server'. 3. Contents of CSP v1.04a 3.1 NetWare v5.1 CSP CPQDPLOY.NLM v1.04a BP000053.XML Bundle installation XML file for CPQDPLOY.NLM CPQDPLOY.TXT This file CP001043.NLM Supports the Compaq Array adapters (CPQARRAY.HAM) CP001044.NLM Supports the Compaq SCSI adapters (CPQSCSI.HAM) CP001045.NLM Supports the Adaptec 160M adapters (ADPT160M.HAM) CP001046.NLM Supports the Compaq Fibre Channel Adapters (CPQFC.HAM) CP001047.NLM Supports the Compaq NetFlex-3 Ethernet Adapters (CPQNF3.LAN) CP001048.NLM Supports the Compaq Netelligent Token-Ring Adapters (CPQTRODI.LAN) CP001049.NLM Supports the IBM 16/4 Token-Ring Adapters (IBMTRPO.LAN) CP001050.NLM Supports the Compaq N100 Fast-Ethernet Adapters (N100.LAN) CP001051.NLM Supports the Compaq N1000 Gigabit Ethernet Adapters (N1000.LAN) CP001052.NLM Supports the SysKonnect FDDI Adapters (SKFPNW.LAN) CP001053.NLM Supports the AMD ISA Ethernet Adapters (PCNTNW.LAN) CP001054.NLM Supports the Compaq Remote Insight Adapter (CPQRI.NLM) CP001055.NLM Provides the Compaq Multi-Processor Driver (CPQMPK.PSM) CP001056.NLM Provides the Compaq Health Drivers (CPQHLTH.NLM) CP001057.NLM Provides the Compaq Array Configuration Utility (CPQONLIN.NLM) CP001058.NLM Provides the Compaq Integrated Management Log Viewer (CPQIML.NLM) CP001059.NLM Provides the Compaq Hot-Plug PCI Support (CPQSBD.NLM) CP001060.NLM Provides the Compaq Power Management Utility (CPQPOWER.NLM) CP001061.NLM Provides the Compaq Standby Server Recovery Option support (CPQRSO.NLM) CP001062.NLM Supports the Compaq RAID adapters (CPQRAID.HAM) CP001064.NLM Provides the Enhanced Integrated Management Utility (CPQEIMD.NLM) CP001065.NLM Supports the Compaq MegaIDE IDE adapters (MEGAIDE.HAM) CP001120.NLM Provides the Compaq Foundation Agent (CPQHOST.NLM) CP001121.NLM Provides the Compaq Server Agent (CPQBSSA.NLM) CP001122.NLM Provides the Compaq NIC Agent (CPQNCSA.NLM) CP001123.NLM Provides the Compaq Storage Agent (CQMGSTOR.NLM) CP001124.NLM Provides the Compaq Survey Utility (SURVEY.NLM) 3.2 NetWare v4.2 CSP CPQDPLOY.NLM v1.04a BP000054.XML Bundle installation XML file for CPQDPLOY.NLM CPQDPLOY.TXT This file CP000834.NLM Supports the Compaq Array adapters (CPQARRAY.HAM) CP000835.NLM Supports the Compaq SCSI adapters (CPQSCSI.HAM) CP000836.NLM Supports the Adaptec 160M adapters (ADPT160M.HAM) CP000837.NLM Supports the Compaq Fibre Channel Adapters (CPQFC.HAM) CP000838.NLM Supports the Compaq NetFlex-3 Ethernet Adapters (CPQNF3.LAN) CP000839.NLM Supports the Compaq Netelligent Token-Ring Adapters (CPQTRODI.LAN) CP000840.NLM Supports the IBM 16/4 Token-Ring Adapters (IBMTRPO.LAN) CP000841.NLM Supports the Compaq N100 Fast-Ethernet Adapters (N100.LAN) CP000842.NLM Supports the Compaq N1000 Gigabit Ethernet Adapters (N1000.LAN) CP000843.NLM Supports the SysKonnect FDDI Adapters (SKFPNW.LAN) CP000844.NLM Supports the AMD ISA Ethernet Adapters (PCNTNW.LAN) CP000845.NLM Supports the Compaq Remote Insight Adapter (CPQRI.NLM) CP000846.NLM Provides the Compaq Multi-Processor Driver (CPQSMP.PSM) CP000847.NLM Provides the Compaq Health Drivers (CPQHLTH.NLM) CP000848.NLM Provides the Compaq Array Configuration Utility (CPQONLIN.NLM) CP000849.NLM Provides the Compaq Integrated Management Log Viewer (CPQIML.NLM) CP000850.NLM Provides the Compaq Hot-Plug PCI Support (CPQSBD.NLM) CP000851.NLM Provides the Compaq Power Management Utility (CPQPOWER.NLM) CP000852.NLM Provides the Compaq Standby Server Recovery Option support (CPQRSO.NLM) CP000853.NLM Supports the Compaq RAID adapters (CPQRAID.HAM) CP000856.NLM Provides the Enhanced Integrated Management Utility (CPQEIMD.NLM) CP000858.NLM Supports the Compaq MegaIDE IDE adapters (MEGAIDE.HAM) CP001120.NLM Provides the Compaq Foundation Agent (CPQHOST.NLM) CP001121.NLM Provides the Compaq Server Agent (CPQBSSA.NLM) CP001122.NLM Provides the Compaq NIC Agent (CPQNCSA.NLM) CP001123.NLM Provides the Compaq Storage Agent (CQMGSTOR.NLM) CP001124.NLM Provides the Compaq Survey Utility (SURVEY.NLM) 4. Software Installation The CSP can be installed in one of five ways: o Command-line by CPQDPLOY.NLM (See Section 4.1) o Graphical (NUT-based) by CPQDPLOY.NLM (See Section 4.2) o Command-line by individual package (See Section 4.3) o Graphical (NUT-based) by individual package (See Section 4.4) o CPQSETUP.NLM (Individual Component Installer) after Component Extraction (See Section 4.5) 4.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 Compaq-tested collection of component packages which will deploy device drivers, utilities, agents, or Survey. See Section 4.7 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. 4.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: 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 in the list 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. 4.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 CP001047) preceded by the LOAD command (optional in NetWare v5.1) 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 4.7 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. 4.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: 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 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. 4.5 CPQSETUP.NLM (Individual Component Installer) after Component Extraction If you elect to extract the contents of a component by using the -x[PATH] option, you can still install the contents of the package by executing the CPQSETUP.NLM utility. See Section 4.7 for an example of how to extract a package and execute the CPQSETUP.NLM utility. Once the utility is started, it behaves exactly as an individual component installer as described above in Sections 4.3 and 4.4. Regardless of the command-line option passed, information about the success/failure of the installation is logged in the SYS:\ETC\CPQLOG.LOG file. NOTE: The CPQSETUP.NLM utility does not support multiple packages in the same extracted directory. Placing multiple extracted packages in the same directory will cause the installation to fail. 4.6 List of Command-line parameters NOTE: Parameters can be entered as upper or lower case, with either a slash '/' or dash '-' preceeding 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: CPQDPLOY [/H[ELP]|/?] [/NUI] [/S[ILENT]] [/R[EBOOT]] [/F[ORCE]] [BP000xxx.XML|COMPONENT.NLM] CPQDPLOY [-H[ELP]|-?] [-NUI] [-S[ILENT]] [-R[EBOOT]] [-F[ORCE]] [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. Individual Component command-line parameters: CP00XXXX [/H[ELP]|/?] [/NUI] [/S[ILENT]] [/F[ORCE]] [/I] [/G] [/R[EBOOT]] [/xVOL:\PATH] CP00XXXX [-H[ELP]|-?] [-NUI] [-S[ILENT]] [-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. CPQSETUP.NLM (Individual Component Installer) command-line parameters NOTE: CPQSETUP.NLM is only available after a package has been extracted to a directory. During normal installation, CPQSETUP.NLM will be automatically called by the Individual component extraction utility. CPQSETUP [/H[ELP]|/?] [/NUI] [/S[ILENT]] [/F[ORCE]] [/R[EBOOT]] CPQSETUP [-H[ELP]|-?] [-NUI] [-S[ILENT]] [-F[ORCE]] [-R[EBOOT]] -(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. 4.7 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. In the following example, the packages and bundle file must be in the SYS:\DEPLOY directory. SYS:\DEPLOY\CPQDPLOY o Normal program execution to deploy a bundle of components for NetWare v4.2. The deployment utility will expect the bundle file and all bundles to be in the directory which it was called from. In the following example, the packages and bundle file must be in the SYS:\DEPLOY directory. LOAD SYS:\DEPLOY\CPQDPLOY o Using CPQDPLOY to deploy a bundle LOAD SYS:\DEPLOY\CPQDPLOY BP000053.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\CP001043 o Installing a single component with force and "no user interface" options LOAD SYS:\DEPLOY\CP001053 -f -nui o Extracting a components contents to another directory LOAD SYS:\DEPLOY\CP000845 -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\CP000847 -i o Determining the source directory, destination directory and primary NLM that will be installed by the component package LOAD SYS:\DEPLOY\CP001057 -g o Deploying a single component from the deployment utility with force option LOAD SYS:\DEPLOY\CPQDPLOY CP001043.NLM -f 5. Log files During CSP 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. 6. Troubleshooting CSP installations Issue : On NetWare v4.2, when I try to install using the CSP, I get a message about an undefined public symbol "_closedir_510" Resolution: Download and install the CLIBAUX1.EXE patch off the http://support.novell.com website. This patch is a prerequisite for running the CSP on NetWare v4.2. Issue : When I try to run the CSP, I get a message in the GUI stating "No Support Paq Found". Resolution: The BP0000xx.XML file was not located in the same directory as CPQDPLOY.NLM was executed from. Issue : When the CSP exits, a message is shown similar to the following: 8-06-2001 10:18:34 pm: SERVER-5.0-2715 [nmID=D0003] Module did not release 20416 resources Module: Compaq Extraction Utility Resource: Small Memory Allocations Description: Alloc Memory (Bytes) Resolution: This is a message displayed by the NetWare garbage collector. The memory was not released properly by the CSP and the garbage collector is 'collecting' the memory and placing back into the heap storage for use by other programs. The message is displayed to alert users that an NLM did not finish its cleanup on termination. The cleanup of memory deallocation will be resolved in the next version of the CSP. 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: The key file within each package is version checked before the file is installed on the server. If the key file is newer than the file on the server, then the version in the package will be installed. Otherwise, the version currently installed on the server is retained and the package and all of its contents are NOT installed. *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. 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 CSP, an option will be provided to allow installation even if the software prerequisites that a package requires are not met. Issue: During installation, I receive a "Trace Portal Message" stating "No return status from Component CP00xxxx.NLM". Resolution: This normally occurs because a package did not complete installation within the 90 second window allowed each package. The main cause of this is a corrupt package. If a package cannot be extracted because it was truncated during a download, the installer will be unable to finish the extraction, parsing, or copying. The best way to resolve this is to download the package again from http://www.compaq.com. Issue: During installation, I get error messages about unable to read xxx from an XML file. 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 CSP, 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 CSP 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. 7. Additional Information For additional information about the use of the CSP for Novell NetWare, refer to the following documents: * "Compaq Delivers Compaq Support Paqs for Novell NetWare" white paper, available on the Compaq website: http://www.compaq.com/smartstart * "Using the Compaq Support Paq (CSP) Deployment Utilities to Deploy Compaq Support Software -- Software Maintenance Best Practices" user guide, available on the Compaq website: http://www.compaq.com/manage/rdu.html ----------------------------------------------------------------------------- Copyright 2001 Compaq Computer Corporation Compaq and the Compaq logo Reg. U.S. Pat. & Tm. Off. 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.