ATTENTION If you have the command queueing fastpatch (MSO-4104-00 Patch Tape) already installed, you must deinstall this fastpatch and rebuild the kernel before installing the QCIC V3.4.1 software.
ATTENTION Use the procedure in this section only if you intend to install the operating system from tape on a qd disk. If this is not your intention, skip this section and proceed to Section 3.2 for Symmetry® 2000 systems, or Section 3.3 for Symmetry 5000 systems.
To install QCIC software on DYNIX/ptx 4.4 (or later) systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes, which includes information for installing from CD-ROM.
Use the distribution tape labeled "QCIC SW 3.4.1."
Two types of procedures are provided in this section:
A summary procedure for installers experienced with the ptx/ADMIN® menu system for deinstalling and installing software and experienced with updating firmware in PROMs.
A detailed procedure for installers who have less experience.
If the QCIC, QCIC-W, QCIC-E, or CSM to which you intend to connect the boot disk is not a new board, program the Level-A flash PROMs.
Configure the proper boot string so that the QCIC board or HPSE will load the operational firmware from its flash PROMs instead of attempting to load it from disk.
After completing these steps, install the operating system and the QCIC software on disk, as described in Sections 3.2 and 3.3 of this document.
When the operating system is to be loaded on a qd disk (a disk connected to a QCIC, QCIC-W, QCIC-E, or CSM), the following procedure loads the QCIC software and makes a QCIC board or the HPSE functional. The procedure is to program the Level-B QCIC software into the Level-B flash PROM so that the board can use that code while the operating system is being installed.
Once the operating system is running, the QCIC firmware is installed on the boot disk, and the QCICPath boot string is set to point to the Level-B software on the boot disk.
ATTENTION It is not necessary to program the Level-A flash PROM with the Level-A software unless a new version of the QCIC software is being installed on an existing board.
Boot the system from tape by following the instructions in the SSM/VBAD Software and Diagnostic Executive Release Notes (for Symmetry 2000 systems) or the CSM Software and Diagnostic Executive Release Notes (for Symmetry 5000 systems).
Bring the system to the Level-B prompt (--->). To get to Level-B from Level-A, enter the bs command at the Level-A prompt.
If you are adding new functionality that requires a new version of QCIC software, update (flash) the PROMs with the fprog command. (If you are installing a new QCIC or CSM board, this step should not be required. You may proceed to Step 3.)
ATTENTION If you put incorrect data into the flash PROMs, the board will not be functional next time the system is booted, and the operating system will not be able to access any disk drives connected to that board.
The firmware in the QCIC Level-A flash PROMs is used when the board initially powers up, to verify the internal functionality of the board. The Level-A firmware must be the same version as the QCIC software on the boot disk (Level-B). (Use the config command at the Power-Up Monitor Level-B prompt to check the version numbers of the Level-A and Level-B QCIC software on each QCIC board and the HPSE.) When replacing a QCIC board or the CSM, you must update the QCIC software.
At the Level-B prompt, enter fprog.
Select option 2 from the menu. The SSM, SSM-2, or CSM board SLIC ID will automatically be selected as the default value. Change this to the SLIC ID of the QCIC board on which you intend to program the flash PROMs. If you intend to program the flash PROMs on the HPSE section of the CSM board, change the value to SLIC ID 2.
Select option 1 from the fprog menu to update the flash PROMs and specify a filename.
Select the flash PROM that you want to program:
Which FPROM (0=lvlA 1=lvlB) [0]: 0
When the system asks for the file to program, enter the appropriate string for your system's configuration, as shown in Table 3-1.
System |
Distribution Medium |
Board |
Path |
S2000 |
QCIC Software tape |
QCIC |
tm(56,3) |
QCIC-W |
tm(56,5) |
||
S5000 |
QCIC Software tape |
QCIC-W, QCIC-E, or HPSE |
tq(0x400,5) |
After you select the file, the system displays the following:
Verifying input datachecksum
Programming FPROM at slic address xx, 0x40000 bytes
Using FPROM data file tq(0x400,5)
Continue? (y/n)
(The filename might be different on your system.) If you are satisfied with the selections, enter y to continue. If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or change the SLIC ID. The programming operation can take up to one minute. While the PROMs are being programmed, the system will display the following:
Programming zeros
Erasing FPROM
Programming ..................................
Program the Level-B flash PROM on the QCIC board or HPSE.
Level-B is the program that the QCIC board or HPSE uses to communicate with its SCSI devices and the operating system. Level-B normally resides on the system's boot disk. When the system boots up, the Level-B QCIC software is loaded into system memory, and the HPSE and each QCIC board copies it into onboard RAM. When this software is programmed into the flash PROMs, the QCIC or HPSE can become operational without accessing a disk drive.
Select option 2 from the menu. (If you programmed the Level-A flash PROM the correct SLIC ID is still selected and you can skip this step and proceed with Step b). If you did not need to program the Level-A flash PROM in step 2, the SSM, SSM-2, or CSM board's SLIC ID will automatically be selected as the default value. Change this to the SLIC ID of the QCIC board on which you intend to program the flash PROMs. If you intend to program the flash PROMs on the HPSE section of the CSM board, change the value to SLIC ID 2.
Select option 1 from the fprog menu to update the flash PROMs and specify a filename. Select the flash PROM you want to program as follows:
Which FPROM (0=lvlA 1=lvlB) [0]: 1
When the system asks for the file to program, enter the appropriate path for your system's configuration, as shown in Table 3-2.
System |
Distribution Medium |
Board |
Path |
S2000 |
QCIC Software tape |
QCIC |
tm(56,2) |
QCIC-W |
tm(56,3) |
||
S5000 |
QCIC Software tape |
QCIC-W, QCIC-E, or HPSE |
tq(0x400,4) |
Exit fprog by choosing option "q" from the fprog menu.
Verify or set the QCICPath or QCICFB flag so that the system will boot the QCIC software from the HPSE PROMs:
---> bo QCICPath='wd(0,0)bootfrom flash' (S2000 systems)
or
---> bo QCICFB=yes (S5000 systems)
At the Level-B prompt, enter the following command:
---> pup skip=y
Rerun the power-up tests by typing:
---> ctlr probe
After completing this procedure, install the operating system according to the instructions in the DYNIX/ptx Base Operating System Installation Guide, and install the QCIC software on the boot disk, as described in Section 3.2 for Symmetry 2000 systems, and in Section 3.3 for Symmetry 5000 systems.
Use the distribution tape labeled "QCIC SW 3.4.1."
Two types of procedures are provided in this section:
A summary procedure for installers experienced with the ptx/ADMIN menu system for deinstalling and installing software and experienced with updating firmware in PROMs.
A detailed procedure for installers who have less experience.
Each step in the Summary Procedure correlates to the same step number in the Detailed Procedure, so that users of the Summary Procedure can easily refresh their memories on any step as needed.
Make sure that there is a correct directory structure (/usr/ssw/fw/qcic/opfw) on the disk where the QCIC software will be loaded.
From single-user mode, use the ptx/ADMIN menu system to install the new version of the QCIC software from the distribution CD. Do not boot the operating system to multi-user at this time.
Take the system down to Level-B of the Power-Up Monitor. If in multi-user mode, use the shutdown command. If in single-user mode, use init 0. Do not use Ctrl-P.
Set up the system boot strings for subsequent boots. For clustered systems, verify that the ptx/CLUSTERSTM init file is set correctly.
Update the QCIC board Level-A flash PROMs with fprog. (This step is not required for new systems or new QCIC boards, or if you followed the procedure in Section 3.1.)
Boot the operating system with the bh command.
The QCIC software must be installed on the boot disk (usually a wd disk connected to the SSM or SSM-2 SCSI bus). The installation script (which is automatically run by the ptx/ADMIN menu system) puts the QCIC software into the /usr/ssw/fw/qcic/opfw directory.
You must first verify that a /usr/ssw directory has been created and mounted on the disk, and that the SSM software has been installed. This filesystem may be mounted directly on partition /dev/dsk/wd0s2, or it may use /usr/ssw as a link to a directory that resides in a qd filesystem. (A qd filesystem is any filesystem that resides on a disk connected to a QCIC port.)
Install the new software.
The following instructions assume that you are familiar with the ptx/ADMIN menu system which installs and deinstalls software. If you have not used the installation procedure or have questions about it, refer to the DYNIX/ptx Software Installation Guide for more information.
To install the QCIC software, complete these steps:
Insert the distribution medium into the appropriate drive.
ATTENTION Use the distribution tape labeled "QCIC Software - V3.4.1."
Log in as root or use the su command to become the superuser.
Use the wall command to notify users that the system will be going down to single-user mode for the software upgrade.
Use init 1 to go to the single-user level.
Mount the /usr filesystem:
# mount /usr
Enter the ptx/ADMIN menu system:
# menu
Choose the System Administration menu.
Choose the Software Management menu.
ATTENTION To install QCIC software on DYNIX/ptx 4.4 (or later) systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes which includes information for installing from CD-ROM.
The installation device must match your distribution medium. If necessary, use the Change Installation Device option in the Software Management menu to change to tape.
Select the Preview Software Package option. For the installation procedure, the name of this product is qcic.
The preview and installation phases of the installation script produce output that is specific for the system type. The output examples in this procedure may differ in terms of drive unit numbers, file space requirements, and boot string information during the actual installation.
Run the preview phase.
The Bill of Materials (BOM) and other installation files are loaded into the /usr/options/qcic directory. The preview log is named /usr/options/qcic/preview.log. To read this file, use the Edit/View Preview Log option from the Software Management menu.
If the preview phase reports that files are in conflict or will be deleted, be sure to examine the preview log to determine whether you need to take any action to resolve the conflicts or to save files.
The preview phase of the installation script produces output similar to the following example:
Rewinding the tape ... Installation script, preview step, for QCIC SW 3.4.1 Filesystem /usr 41611 K free 70 K space needed to do install 0 K required to preload conflicts 11075 K required to preload all files 0 K required to save old files
Run the preload phase. You may skip this phase if your system is low on disk space.
ATTENTION The /usr/options/qcic/newfiles directory is the default location for preloaded files. If the newfiles directory contains preloaded files from an earlier version of this software, be sure to move or delete the directory before you start the preload phase.
When the preload phase is complete, you can examine the preloaded files. To resolve file conflicts, merge the local information from the files on the system into the preloaded files.
Run the install phase.
ATTENTION The /usr/options/qcic/oldfiles directory is the default location for saving locally modified files. If the oldfiles directory currently contains files saved from an earlier version of this package, be sure to move or delete the directory before you start the install phase.
Select the Install Software Package option of the Software Management menu to run the install phase. During the installation phase, note the online caution about updating QCIC PROMs before rebooting.
ATTENTION In the following example, all of /usr is installed in the same wd partition. If the /usr/ssw filesystem is a link, the output script will not show the "wd(0,2)ssw/" portion of the path.
Installation script, install step, for QCIC SW 3.4.1 Your options for continuing are: 1)Install files without preserving locally modified files that are overwritten or deleted. 2)Install files preserving locally modified files that are overwritten or deleted. How would you like to proceed? 1 Installing QCIC fw... SSM Firmware boot strings: bo QCICPath:"wd(0,2)ssw/fw/qcic/opfw" QCIC level A Flash Prom data file:"wd(0,2)ssw/fw/qcic/prom.bin" QCIC level B Flash Prom data file:"wd(0,2)ssw/fw/qcic/opfw.bin" QCIC-W level A Flash Prom data file:"wd(0,2)ssw/fw/qcic/prom256k.bin" QCIC-W level B Flash Prom data file:"wd(0,2)ssw/fw/qcic/opfw256k.bin" The bootstring info is captured in /usr/options/qcic/BOOTSTRING-INFO Press RETURN to redisplay menu
When the install phase is complete, you can resolve file conflicts by merging local information from the saved files into the files now on the system.
ATTENTION Do not reboot the system immediately after this step.
Go to Level-B of the Power-Up Monitor.
ATTENTION Do not use Ctrl-P to go from the operating system to Level-B in this procedure. This command leaves the operating system running in the background. The fprog utility will display a warning message and will not run until the operating system is shut down.
Use the ptx/ADMIN menu system to take the system to the firmware level (Level-B).
An alternative to the menu system is to issue the following command from multiuser mode:
shutdown -y -g120 -i0
ATTENTION You can issue init 0 directly if you are sure there are no other users on the system.
From single-user mode, use the following command:
init 0
Set up the boot strings.
Make sure that the power-up monitor boot strings are set to the same paths as listed in the output from the installation script, as shown in Step 2.
During installation, the system displayed the name of each product as it was installed and listed the path for the boot strings. That boot string information was also captured and saved in the file /usr/options/qcic/BOOTSTRING-INFO.
You can look at the current values of the QCIC software boot strings by using the print command from the Level-B prompt as follows:
---> printbo
If any of the boot strings are different from those listed in /usr/options/qcic/BOOTSTRING-INFO, you must change them to match the output from the installation script. For example:
---> bo QCICPath=wd(0,2)ssw/fw/qcic/opfw
ATTENTION If the QCIC software is moved to a different disk or partition after initial installation, you must revise the BOOTSTRING-INFO file so that it will provide accurate boot string path information for later reference. If you are using the ptx/CLUSTERS product, you may also need to update the /usr/ssw/fw/qcic/info.xx files (refer to Appendix A). This is required only if you are using shared tape devices or if you are mixing 5.25-inch and 3.5-inch Pbays in a cluster of more than two nodes. The ptx/CLUSTERS Installer's Guide contains procedures for making these modifications.
ATTENTION It should not be necessary to install the Level-A QCIC software on new systems-skip the next step in this procedure if you are installing a new system or if you have already followed the procedure in Section 3.1. If you are upgrading from an earlier version of the QCIC software, install the QCIC Level-B software on disk, and program the QCIC board Level-A flash PROM with the QCIC Level-A software.
Update the QCIC board Level-A flash PROMs.
ATTENTION If you put incorrect data into the flash PROMs, the board will not be functional next time the system is booted, and the operating system will not be able to access any disk drives connected to that board.
The firmware in the QCIC Level-A flash PROMs is used when the board initially powers up, to verify the internal functionality of the board. The Level-A firmware must be the same version as the QCIC software on the boot disk (Level-B). When replacing a QCIC board, you must update the QCIC software.
Use the config command at the Power-Up Monitor Level-B prompt to compare version numbers of QCIC software being installed to versions already installed on each QCIC board. (config is accurate only if zap, ctlr probe, or a power-cycle has been invoked since installing the new QCIC software.)
If you are adding new functionality that requires a new version of QCIC software, update (flash) the PROMs with the fprog command.
Before beginning this procedure, find the path for the Level-A software in the file /usr/options/qcic/BOOTSTRING-INFO. The Level-A software is contained in a file named prom.bin (for QCIC boards) or prom256k.bin (for QCIC-W boards).
To update the flash PROMs on the QCIC board, follow these steps:
Bring the system to the Level-B prompt (--->). To get to Level-B from Level-A, enter the bs command at the Level-A prompt.
To get to Level-B when DYNIX/ptx is running in multiuser or single-user mode, you must shut down the operating system. From multiuser mode, enter:
shutdown -y -g120 -io
ATTENTION You can issue init 0 directly if you are sure there are no other users on the system.
From single-user mode, enter:
init 0
ATTENTION Do not use Ctrl-P to go from the operating system to Level-B in this procedure. Ctrl-P leaves the operating system running in the background, and fprog will not run if the operating system is running.
Display the system configuration by typing the config command at the Level-B prompt (--->). (config is accurate only if zap, ctrl probe, or a power-cycle has been invoked since installing the new QCIC software.) The configuration entry for the each QCIC board shows two version numbers marked Aver (firmware in PROMs) and Bver (software on disk). If Aver shows a version earlier than Bver, you must update the flash PROMs.
ATTENTION If you put incorrect data into the flash PROMs, the QCIC board will not be functional next time the system is booted.
At the Level-B prompt, enter fprog.
Select option 2 from the menu. The SSM or SSM-2 board SLIC ID will automatically be selected as the default value. Change this to the SLIC ID of the QCIC board on which you intend to program the flash PROMs.
Select option 1 from the fprog menu to update the flash PROMs and specify a filename. Refer to Table 3-3 for the default location of this file on a particular platform.
System |
Location of Software |
Board |
Path |
S2000/2x0 |
Boot Disk |
QCIC |
wd(0,2)/ssw/fw/qcic/prom.bin |
QCIC-W |
wd(0,2)/ssw/fw/qcic/prom256k.bin |
||
S2000/4x0 and S2000/7x0 |
Boot Disk |
QCIC |
wd(0,0)/ssw/fw/qcic/prom.bin |
QCIC-W |
wd(0,0)/ssw/fw/qcic/prom256k.bin |
||
All S2000 |
QCIC Software tape |
QCIC |
tm(56,4) |
QCIC-W |
tm(56,5) |
After you select the file, the system displays the following:
Verifying input datachecksum
Programming FPROM at slic address xx, 0x40000 bytes
Using FPROM data file wd(0,0)ssw/fw/qcic/prom256k.bin
Continue?(y/n)
(The filename might be different on your system.) If you are satisfied with the selections, enter y to continue. If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or to change the SLIC ID. The programming operation can take up to one minute. While the PROMs are being programmed, the system will display the following:
Programming zeros
Erasing FPROM
Programming ..................................
Exit fprog by choosing option "q" from the fprog menu.
The new firmware will not take effect until the system is power-cycled. After running fprog, simulate a system power cycle by executing the zap command:
---> zap
If the monAuto boot flag has been set to 0, the system reboot will stop at Level-A. To get to Level-B enter:
-> bs
Then boot the operating system by entering:
---> bh
If the monAuto boot flag has been set to 1, the system will automatically come up to Level-B. Then enter the following command to boot the operating system:
---> bh
Boot the operating system.
At the Level-B prompt, enter bh to boot the operating system.
Use the distribution tape labeled "QCIC SW 3.4.1."
Two types of procedures are provided in this section:
A summary procedure for installers experienced with the ptx/ADMIN menu system for deinstalling, installing, and updating software.
A detailed procedure for less-experienced installers.
Each step in the Summary Procedure correlates to the same step number in the Detailed Procedure.
Make sure there is a correct directory structure (/usr/ssw/fw/qcic/opfw) on the disk where the QCIC software will be loaded.
From single-user mode, use the ptx/ADMIN menu system to install the new version of the QCIC software from the distribution CD. Do not boot the operating system to multi-user at this time.
Take the system down to Level-B of the Power-Up Monitor. If in multi-user mode, use the shutdown command. If in single-user mode, use init 0. Do not use Ctrl-P.
Set up the system boot strings for subsequent boots. For clustered systems, verify that the ptx/CLUSTERS init file is set correctly.
Update the HPSE, QCIC-W, and QCIC-E board Level-A flash PROMs with fprog. (This step is not required for new systems or new QCIC and CSM boards, or if you followed the procedure in Section 3.1.)
Boot the operating system with the bh command.
The QCIC software must be installed on the boot disk (usually a qd disk connected to the CSM channel 0 SCSI bus). The installation script (which is automatically run by the ptx/ADMIN menu system) puts the QCIC software in the /usr/ssw/fw/qcic/opfw directory.
You must first verify that a /usr/ssw directory has been created and mounted on the disk, and that the CSM software has been installed. This filesystem may be mounted directly on partition /dev/dsk/qd0s2, or it may use /usr/ssw as a link to a directory that resides on a disk other than the boot disk.
Install the new software.
The following instructions assume that you are familiar with the ptx/ADMIN menu system which installs and deinstalls software. If you have not used the installation procedure or have questions about it, refer to the DYNIX/ptx Software Installation Guide for more information.
To install the QCIC software, complete these steps:
Insert the distribution medium into the appropriate drive.
Log in as root or use the su command to become the superuser.
Use the wall command to notify users that the system will be going down to single-user mode for the software upgrade.
Use init 1 to go to the single-user level.
Mount the /usr filesystem:
# mount /usr
Enter the ptx/ADMIN menu system:
# menu
Choose the System Administration menu.
Choose the Software Management menu.
ATTENTION To install QCIC software on DYNIX/ptx 4.4 (or later) systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes which includes information for installing from CD-ROM.
The installation device must match your distribution medium. If necessary, use the Change Installation Device option in the Software Management menu to change to tape.
Select the Preview Software Package option. For the installation procedure, the name of this product is qcic.
The preview and installation phases of the installation script produce output that is specific for the system type. The output examples in this procedure may differ in terms of drive unit numbers, file space requirements, and boot string information during the actual installation.
Run the preview phase.
The Bill of Materials (BOM) and other installation files are loaded into the /usr/options/qcic directory. The preview log is named /usr/options/qcic/preview.log. To read this file, use the Edit/View Preview Log option from the Software Management menu.
If the preview phase reports that files are in conflict or will be deleted, be sure to examine the preview log to determine whether you need to take any action to resolve the conflicts or to save files.
The preview phase of the installation script produces a dialog similar to the following example:
Rewinding the tape ... Installation script, preview step, for QCIC SW 3.4.1 Filesystem /usr 41611 K free 70 K space needed to do install 0 K required to preload conflicts 11075 K required to preload all files 0 K required to save old files
Run the preload phase. This phase is optional if your system is low on disk space.
ATTENTION The /usr/options/qcic/newfiles directory is the default location for preloaded files. If the newfiles directory contains preloaded files from an earlier version of this software, be sure to move or delete the directory before you start the preload phase.
When the preload phase is complete, you can examine the preloaded files. To resolve file conflicts, merge the local information from the files on the system into the preloaded files.
Run the install phase.
ATTENTION The /usr/options/qcic/oldfiles directory is the default location for saving locally modified files. If the oldfiles directory currently contains files saved from an earlier version of this package, be sure to move or delete the directory before you start the install phase.
Select the Install Software Package option of the Software Management menu to run the install phase. During the installation phase, note the online caution about updating QCIC PROMs before rebooting.
ATTENTION In the following example, all of /usr is installed in the same qd partition. If the /usr/ssw filesystem is a link, the output script will not show the "qd(0,2)ssw/" portion of the path.
Installation script, installstep, for QCIC SW 3.4.1
Your options for continuing are:
1) Install files without preserving locally modified files that are
overwritten or deleted.
2) Install files preserving locallymodified files that are
overwritten or deleted.
How would you like to proceed? 1
Installing QCIC fw...
SSM Firmware Monitor boot strings:
bo QCICPath:"qd(0,2)ssw/fw/qcic/opfw"
QCIC or HPSE level A Flash Prom data file:"qd(0,2)ssw/fw/qcic/prom256k.bin"
QCIC or HPSE level B Flash Prom data file:"qd(0,2)ssw/fw/qcic/opfw256k.bin"
The bootstring info is captured in /usr/options/qcic/BOOTSTRING-INFO
Press RETURN to redisplay menu
When the install phase is complete, you can resolve file conflicts by merging local information from the saved files into the files now on the system.
ATTENTION Do not reboot the system immediately after this step.
Go to Level-B of the Power-Up Monitor.
ATTENTION Do not use Ctrl-P to go from the operating system to Level-B in this procedure. This command leaves the operating system running in the background. The fprog utility will display a warning message and will not run until the operating system is shut down.
Use the ptx/ADMIN menu system to take the system to the firmware level (Level-B).
An alternative to the menu system is to issue the following command from multiuser mode:
shutdown -y -g120 -i0
ATTENTION You can issue init 0 directly if you are sure there are no other users on the system.
From single-user mode use the following command:
init 0
Set up the boot strings.
Make sure that the power-up monitor boot strings are set to the same paths as listed in the output from the installation script, as shown in Step 2.
During installation, the system displayed the name of each product as it was installed and listed the path for the boot strings. That boot string information was also captured and saved in the file /usr/options/qcic/BOOTSTRING-INFO.
You can look at the current values of the QCIC software boot strings by using the print command from the Level-B prompt as follows:
---> printbo
If any of the boot strings are different from those listed in /usr/options/qcic/BOOTSTRING-INFO, you must change them to match the output from the installation script. For example:
---> bo QCICPath=qd(0,2)ssw/fw/qcic/opfw
ATTENTION If the QCIC software is moved to a different disk or partition after initial installation, you must revise the BOOTSTRING-INFO file (refer to Appendix Aso that it will provide accurate boot string path information for later reference.
If you are using the ptx/CLUSTERS product, you may also need to update the /usr/ssw/fw/qcic/info.xx files. This is required only if you are using shared tape devices or if you are mixing 5.25-inch and 3.5-inch Pbays in a cluster of more than two nodes. The ptx/CLUSTERS Installer's Guide contains procedures for making these modifications.
ATTENTION It should not be necessary to install the Level-A QCIC software on new systems-skip the next step in this procedure if you are installing a new system or if you have already followed the procedure in Section 3.1. If you are upgrading from an earlier version of the QCIC software, install the QCIC Level-B software on disk, and program the HPSE and QCIC board Level-A flash PROMs with the QCIC Level-A software.
Update the QCIC or HPSE board Level-A flash PROMs.
ATTENTION If you put incorrect data into the flash PROMs, the HPSE or the QCIC board will not be functional next time the system is booted.
The firmware in the HPSE and QCIC Level-A flash PROMs is used when the board initially powers up, to verify the internal functionality of the board. The Level-A firmware must be the same version as the QCIC software on the boot disk (Level-B). When replacing a QCIC board or the CSM, you must update the QCIC software.
Use the config command at the Power-Up Monitor Level-B prompt to check the version numbers of the Level-A and Level-B QCIC software on each QCIC board and on the HPSE. (config is accurate only if zap, ctrl probe, or a power-cycle has been invoked since installing the new QCIC software.)
If you are adding new functionality that requires a new version of QCIC software, update (flash) the PROMs with the fprog command.
Before beginning this procedure, find the path for the Level-A software in the file /usr/options/qcic/BOOTSTRING-INFO. The Level-A software is contained in a file named prom256k.bin.
To update the flash PROMs on QCIC-W or QCIC-E board or the HPSE, follow these steps:
Bring the system to the Level-B prompt (--->). To get to Level-B from Level-A, enter the bs command at the Level-A prompt.
To get to Level-B when DYNIX/ptx is running in multiuser or single-user mode, you must shut down the operating system. From multiuser mode, enter:
shutdown -y -g120 -i0
ATTENTION You can issue init 0 directly if you are sure there are no other users on the system.
From single-user mode, enter:
init 0
ATTENTION Do not use Ctrl-P to go from the operating system to Level B in this procedure. Ctrl-P leaves the operating system running in the background, and fprog will not run if the operating system is running.
Display the system configuration by typing the config command at the Level-B prompt (--->). The configuration entry for the HPSE and for each QCIC-W or QCIC-E board shows two version numbers marked Aver (firmware in PROMs) and Bver (software on disk). If Aver shows a version earlier than Bver, you must update the flash PROMs.
ATTENTION If you put incorrect data into the flash PROMs, the HPSE or QCIC board will not be functional next time the system is booted.
At the Level-B prompt, enter fprog.
Select option 2 from the menu. The CSM board SLIC ID will automatically be selected as the default value. Change this to the SLIC ID of the QCIC-W or QCIC-E board on which you intend to program the flash PROMs or to SLIC ID 2 if you are programming the HPSE flash PROMs.
Select option 1 from the fprog menu to update the flash PROMs and specify a filename. The default filename for Symmetry 5000 systems is qd(0x000,0)/ssw/fw/qcic/prom256k.bin.
After you select the file, the system displays:
Verifying input data checksum
Programming FPROM at slic address xx, 0x40000 bytes
Using FPROMdata file qd(0x000,0)ssw/fw/qcic/prom256k.bin
Continue? (y/n)
(The filename might be different on your system.) If you are satisfied with the selections, enter y to continue. If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or change the SLIC ID.
The programming operation can take up to one minute. While the PROMs are being programmed, the system will display the following:
Programming zeros
Erasing FPROM
Programming ..................................
Verifying FPROMchecksum
FPROM programming complete.
Exit fprog by choosing option "q" from the fprog menu.
The new firmware will not take effect until the system is power-cycled. After running fprog, simulate a system power cycle by executing the zap command:
---> zap
If the monAuto boot flag has been set to 0, the system reboot will stop at Level-A. To get to Level-B, enter:
-> bs
Then boot the operating system by entering:
---> bh
If the monAuto boot flag has been set to 1, the system will automatically come up to Level-B. Then enter:
---> bh
to boot the operating system.
Boot the operating system.
At the Level-B prompt, enter bh to boot the operating system.