ATTENTION Versions 4.7 and later require a change in the normal sequence of booting the new software and updating the Flash PROMs on slave SSM-2 or VBAD boards. See the revised software installation procedures in this document for either DYNIX/ptx® distribution media and the revised procedure for updating (flashing) the PROMs. Versions 4.7 and later also require that slave SSM-2 boards must contain Level-B software before their PROMs can be updated to Level-A. A special procedure has been added to these release notes for conditioning replacement slave boards whose PROMs are not already at least V4.7 Level-A.
ATTENTION This information does not appear elsewhere in the documentation set.
These release notes contain information on Version 4.9.2 of the system software (System Services Module or VMEbus Adapter, and Diagnostic Executive software). Read the release notes before installing or running the SSM or VBAD software or the diagnostic tests.
ATTENTION Except where explicitly stated otherwise, the acronym SSM designates both the System Services Module (SSM) of the S16 and S2000/2x0 systems and the System Services Module-2 (SSM-2) of the S2000/4x0 and S2000/7x0 systems.
The following topics are covered in these release notes:
Changes since the previous release.
Installing the system software onto disk from the appropriate distribution CD-ROM or tape.
Conditioning replacement slave SSM-2 boards.
Updating the SSM- or VBAD-board PROMs.
Booting the system software directly from CD-ROM or tape.
Booting a new Diagnostic Executive from CD-ROM, tape, or disk while already at Level-B.
Problem reports for this release of the system software.
Late documentation additions.
Version 4.9.2 Level-B is incompatible with versions of Level-A firmware prior to V4.7 for size reasons. Additionally, you must condition SSM-2 boards used as replacement slave boards in systems with Version V4.7 and later. Follow the procedure in this document.
Version 4.9.2 is compatible with:
All SSM and SSM-2 boards in S2000 systems. This software is not compatible with SCED-based systems or systems that contain Balance® processor boards.
All VBAD boards in S5000 systems.
The DYNIX/ptx operating system.
Version 4.9.2 includes all the functionality of the preceding Version 4.9 release, plus the following new feature and functionality:
Allows the OS bootstrings osPath, tmpPath, and auxPath to start with slic (in addition to the standard qd(0,0) as the device identifier). As in previous releases, you can still precede the bootstring with 1 or 2 optional hexadecimal digits to specify a boot flag. This new feature is to support DYNIX/ptx V4.4 and later.
Non-OS bootstrings must still begin with qd(0,0). The new device identifier prefix applies only to the 3 bootstrings used by the loader. The bh command also accepts the new prefix to identify a bootstring. Following are examples of the new prefix:
slic(22,0)scsi(8,0)disk(1,0)
'slic(22,0)scsi(8,0)disk(1,3) -s slic(22,0)scsi(7,0)disk(0,0)'
'88slic(22)scsi(8)disk()dump -f /etc/dumplist'
Adds read-only support for ptx/Enhanced File SystemTM V1.2 (ptxTM/EFS V1.2).
Adds support for DYNIX/ptx V4.2 and later filesystems. Prior to this release, the SSM software could not write to DYNIX/ptx V4.2 or later filesystems.
Adds support for the new ptx/INSTALL (c_dist) installation process for DYNIX/ptx V4.4 and later. The ptxmd installation process is still supported for earlier versions of the operating system.
Initializes the daylight savings time bit in the SSM clock chip.
Adds ptx/SVM (ptx/SVM) support for disks without VTOC. You can specify the starting disk sector with wd(0:sector_num).
Changes the default behavior from scan dump to core dump.
Adds support for 6x and 12x CD-ROM drives.
Removes support for bfs to increase available memory space.
The SSM/CSM Power-Up Monitor Guide explains how to use the SSM/VBAD/CSM power-up monitor software.
The Diagnostic Executive User's Guide explains how to use the diagnostics.
The ptx/INSTALL Software Installation Guide and the DYNIX/ptx and Layered Product Software Installation Release Notes explain how to deinstall and install software in the DYNIX/ptx enviroment.
If your shipment is incomplete or you encounter problems while installing the system software, contact your Customer Support representative.
ATTENTION There is a separate procedure for upgrading SSM software for VBAD boards in S5000 systems. See Section 1.7 of this document.
Use the distribution medium containing the software for SSM V4.9.2.
ATTENTION For SSM/VBAD System Software Versions 4.7 and later, the installation sequence is different from that of previous releases. Do not boot the new Level-B software on slave SSM-2 boards until all the SSM-2 PROMs have been updated using the fprog command. If this sequence is not followed, slave SSM-2 boards will not be able to boot to Level-B. Recovery will require reinstalling a previous Level-B on the slave boards and running fprog again. See Section 1.8.2 of these release notes for the recovery procedure.
ATTENTION To install SSM software on DYNIX/ptx systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes.
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 users of the Summary Procedure can easily refresh their memories on any step as needed.
Make sure that there is a correct /usr/ssw directory structure on a wd disk where the system software will be loaded.
From the single-user level, use the ptx/ADMIN menu system to deinstall the old version of SSM software.
Use the ptx/ADMIN menu system to install the new version of the SSM software from the distribution medium containing SSM V4.9.2. Do not boot to the operating-system level at this time.
Take the system down to Level-B of the Power-Up Monitor. If in multiuser mode, use the shutdown command. If in single-user mode, use init 0. Do not use Ctrl-P.
Set up the SSM bootstrings for subsequent boots.
Update ALL SSM boards' Flash PROMs with fprog. Quit fprog and boot a new Level-B using the zap command to simulate a system power cycle. Stop the boot at Level-B.
From Level-B, use the config command to verify that the Aver and Bver values match for every SSM board listed in the system.
Boot the operating system with the bh command.
Configure the diagnostics for clustered or HIAV (High Availability) systems. Update script files to enable Diagnostic Executive use with clustered or HIAV systems.
The system software must be installed in a /usr/ssw directory on a wd disk. The installation script expects to find a /usr/ssw filesystem in a partition of the wd disk drive (5.25-inch SCSI) that is connected to the SSM board that supports the system console.
Set up a new directory structure if all of /usr currently resides on a zd or qd disk.
ATTENTION If a /usr filesystem is already mounted on a wd disk, skip this step and start the installation with Step 2
Create a /usr/ssw directory structure in partition /dev/dsk/wd0s2 of the wd disk and mount it as a filesystem.
After creating the /usr/ssw directory, create a /usr/ssw/diag directory and a /usr/ssw/fw directory.
Deinstall the existing SSM software.
The following instructions assume that you are familiar with the ptx/ADMIN menu system which is used to install and deinstall 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 deinstall the SSM software, complete these steps:
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, as follows:
% init 1
The init 1 command unmounts the filesystems required by the ptx/ADMIN menu system. So you must re-mount the /usr filesystem as follows:
# mount /usr
Enter the ptx/ADMIN menu system:
# menu
Choose the System Administration menu.
Choose the Software Management menu.
Choose the Remove Software Package option.
At the first prompt, which asks for the name of the package you wish to remove, press F8 (the Select key) for a list of the software currently installed on your system.
Scroll to the entry for ssm, select it, and press F1 (Run).
When asked if you want to remove files in conflict, answer n.
When the deinstallation is finished, return to the Software Management menu.
Install the new software.
ATTENTION To install SSM software on DYNIX/ptx systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes.
Insert the distribution medium into the appropriate drive.
ATTENTION Use the distribution medium containing software for SSM V4.9.2.
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 or CD-ROM as appropriate.
Select the Preview Software Package option. For the installation procedure, the name of this product is ssm.
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 bootstring information during the actual installation.
Another change is that questions about the Diagnostic Executive and about installing a duplicate of the SSM firmware in a reserved disk partition, formerly asked during the installation phase, are now asked in the preview phase.
Run the preview phase.
The Bill of Materials (BOM) and other installation files are loaded into the /usr/options/ssm directory. The preview log is named /usr/options/ssm/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 actions to resolve the conflicts or to save files.
The preview phase of the installation script produces an output similar to the following example:
Previewing ssm from tape ... Rewinding the tape ... Installation script, preview step, for SSM SW 4.9.2 Install SSM Diagnostic Executive? [y] : Filesystem /usr 23449 K free 70 K space needed to do an install 0 K required to preload conflicts 15694 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/ssm/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/ssm/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 new online caution about updating SSM PROMs before rebooting the system and the new script format naming the boot strings.
ATTENTION In the following example, all of /usr is installed in the same wd partition. If only the /usr/ssw filesystem is installed in the partition, then the output script would not show the wd(0,2)ssw portion of the path.
Installing SSM Firmware ...
****************************************************************
* CAUTION *
* *
* The SSM Flash PROMs MUST be updated before rebooting the *
* system. The Flash PROM update procedure is described in *
* the SSM Software Release Notes. *
* *
****************************************************************
SSM Firmware Monitor boot strings:
bs lvlBPath: "wd(0,2)ssw/fw/ssm/lvlB"
bs diagPath: "wd(0,2)ssw/diag/ssm/exec"
bs lvlBTests: "wd(0,2)ssw/fw/ssm/"
bo ssmSlavePath: "wd(0,2)ssw/fw/ssm/lvlB"
bh loaderPath: "wd(0,2)ssw/boot"
SSM Flash Prom data file: "wd(0,2)ssw/fw/ssm/lvlA.rom"
The bootstring info is captured in
/usr/options/ssm/BOOTSTRINGS-INFO
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 multi-user mode:
shutdown -y -g120 -i0
From single-user mode use the following command:
init 0
Set up the bootstrings.
Make sure that the power-up monitor bootstrings are set to the same paths as listed in the output from the system-specific installation script.
ATTENTION If the boot filesystem is EFS-type or will be created as an EFS-type, then the bootstring for lvlBPath must point to the UFS duplicate of Level-B in the reserved disk partition of the boot disk, for instance, wd(x,32), where x stands for a bootable disk connected to the SSM board. Set the bootstring to point to this location instead of the normal location created by the installation script.
During installation, the system displayed the name of each product as it was installed and listed the path for the bootstrings. That bootstring information was also captured and saved in the file /usr/options/ssm/BOOTSTRING-INFO.
ATTENTION If the SSM software is moved to a different disk or partition after initial installation, the BOOTSTRING-INFO file will not provide accurate bootstring path information for later reference.
You can look at the current values of the bs, bo, and bh bootstrings by using the print command from the Level-B prompt. For example:
---> print bs
---> print bo
---> print bh
If any of the bootstrings are different, you must change them to match the output from the installation script, with the exception of the lvlBPath for an EFS-type boot filesystem as explained in the preceding Caution statement.
ATTENTION With the release of SSM Software Version 4.6, the path for diagPath was changed to add the ssm directory between the diag and exec directories. If the current path is different from the one in the installation script, you must change the bootstring for diagPath.
Update the SSM board PROMs.
ATTENTION If you put incorrect data into the Flash PROMs, the system will not boot up on the next power cycle.
At the Level-B prompt, type fprog.
Update the Flash PROMs of the master SSM board first.
ATTENTION In systems with more than one SSM-2 board, the master SSM-2 will be identified as board number 0 in the config display, and it will have the lowest SLIC ID of all SSM-2s in the system by virtue of its card-cage location. The SLIC ID of the master SSM board will always be the default value listed in option 2 of the fprog menu.
Select option 2 from the menu. The master SSM board SLIC ID will automatically be displayed as the default value in the brackets. (This default can be overridden by entering another value.)
Select option 0 from the fprog menu to read the PROM type from the selected board. If the manufacturing code is:
Mfg. code = 0x42EB
it means that the board is an early-version SSM board with non-flashable UV PROMs that must be replaced to update the firmware. All other values of manufacturer and device codes mean that the PROM is programmable.
Select option 1 from the fprog menu to update the Flash PROMs and specify a filename.
Typically, the file to program into the Flash PROM will be one of the following:
wd(0,2)ssw/fw/ssm/lvlA16.rom (for S16 or S2000/2x0)
wd(0,2)ssw/fw/ssm/lvlA.rom (for S2000/4x0 or S2000/7x0)
ATTENTION If only the /usr/ssw filesystem is installed in the partition, then the output script would not show the wd(0,2)ssw portion of the path.
After you select the file, the system displays:
Verifying input data checksum Ready to program FPROM at slic address xx, 0x40000 bytes Continue? (y/n)
If you are satisfied with the selections, type y to continue. If you want to make a change, type 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 FPROM checksum FPROM programming complete.
Update any slave SSM-2 or VBAD boards.
Choose option 2 from the fprog menu and override the default value by entering the SLIC ID of a slave SSM-2 board from the config display. Repeat Steps 6 c through 6 e until all SSM PROMs have been updated to match the SSM software version.
ATTENTION If any slave board PROMs are not updated at this time, they cannot be updated later without reinstalling a previous release of Level-B software (for instance, V4.6.1) on those boards and running fprog again. Section 1.8.2 of these release notes provides a recovery procedure.
Quit fprog.
Exit fprog by choosing option q from the fprog menu.
Verify matching Level-A and Level-B versions.
Boot a new Level-B using the zap command to simulate a system power cycle. Stop the boot at Level-B.
At the Level-B prompt, enter config and verify that all SSM boards in the system have matching Aver and Bver values.
ATTENTION If the Bver value does not match the Aver value for any slave SSM board, you must reinstall Level-B software compatible with V4.9.2 Level-A before the slave board PROMs can be flashed with V4.9.2 Level-A. See the recovery procedure in Section 1.8.2 of these release notes. After performing that recovery, return to Step 6 and complete this upgrade procedure.
Reboot the operating system.
At the Level-B prompt, enter bh to boot the operating system.
Configure the diagnostics for clustered or HIAV systems.
ATTENTION With the release of SSM Software Version 4.6, the path to the script files was changed to add the ssm directory after the diag directory.
If the system being upgraded is part of a cluster or a HIAV (high-availability) system, you must edit the following files after installing the Diagnostic Executive software:
/usr/ssw/diag/ssm/script
/usr/ssw/diag/ssm/script.auto
to include the following line:
cc y
This line must appear in these two script files before any other commands in the script files. Refer to your Diagnostic Executive User's Guide for details about the cc y command.
Even though the VBAD board is installed in a CSM-based S5000 system only, it is driven with SSM software. Use the distribution medium containing software for SSM V4.9.2.
Two types of procedures are provided in this section:
A summary procedure for installers experienced with using the ptx/ADMIN menu system for deinstalling and installing software and experienced with updating firmware in PROMs.
A detailed procedure for installers with less experience.
Each step in the Summary Procedure correlates to the same step number in the Detailed Procedure, so users of the Summary Procedure can easily refresh their memories on any step as needed.
Each step in this procedure correlates to the same step in the detailed procedure in case more detail is needed.
From the single-user level of the operating system, set up the correct directory structure on a qd disk where the system software will be loaded.
From the root account, use the ptx/ADMIN menu system to deinstall the old version of SSM software.
Use the ptx/ADMIN menu system to load the new version of the SSM software from the distribution media containing SSM V4.9.2. Do not reboot the system at this time.
Take the system down to Level-B (also called the firmware level) of the Power-Up Monitor. If in multiuser mode, use the shutdown command. If in single-user mode, use init 0. Do not use Ctrl-P.
Set up the VBAD bootstrings for subsequent boots.
Update all VBAD boards' Flash PROMs with fprog. Quit fprog and boot a new Level-B using the zap command to simulate a system power cycle. Stop the boot at Level-B.
From Level-B, use the config command to verify that the Aver and Bver values match for every VBAD board listed in the system.
Boot the operating system with the bh command.
The system software must be installed on the boot qd disk connected to CSM channel 0. The installation script expects to find a /usr/ssw filesystem in a partition on the qd disk.
Set up the directory structure if necessary.
ATTENTION If the /usr filesystem is already mounted on the qd disk connected to channel 0 of the CSM, skip this step and start the installation with Step 2
You must first create a /usr/ssw directory on the boot qd disk. You can either create and mount this filesystem on partition /dev/dsk/qd0s2.
After creating /usr/ssw, create a /usr/ssw/diag directory and a /usr/ssw/fw directory.
Deinstall the existing SSM software.
The following instructions assume that you are familiar with the ptx/ADMIN menu system, which is used to install and deinstall software. The DYNIX/ptx Software Installation Guide describes the installation procedure and tells how to use the menu system. 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 deinstall the SSM software, complete these steps.
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, as follows:
% init 1
The init 1 command unmounts the filesystems required by the ptx/ADMIN menu system. So you must re-mount the /usr filesystem as follows:
# mount /usr
Enter the ptx/ADMIN menu system:
# menu
Choose the System Administration menu.
Choose the Software Management menu.
Choose the Remove Software Package option.
At the first prompt, which asks for the name of the package you wish to remove, press F8 (the Select key) for a list of the software currently installed on your system.
Scroll to the entry for ssm, select it, and press F1 (Run).
When asked if you want to save files in conflict, answer n.
When the deinstallation is finished, return to the Software Management menu.
Install the new software.
Insert the distribution medium into the appropriate drive.
ATTENTION Use the system software distribution containing SSM V4.9.2.
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 or CD-ROM as appropriate.
Select the Preview Software Package option. For the installation procedure, the name of this product is ssm.
The preview and installation phases of the V4.9.2 installation script have been changed to 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 bootstring information during the actual installation.
Run the preview phase.
The Bill of Materials (BOM) and other installation files are loaded into the /usr/options/ssm directory. The preview log is named /usr/options/ssm/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 actions to resolve the conflicts or to save files.
Run the preload phase (optional).
ATTENTION The /usr/options/ssm/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 this 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.
ATTENTION The /usr/options/ssm/oldfiles directory is the default location for saving locally modified files. If the oldfile 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.
Run 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 new online caution about updating VBAD PROMs before rebooting the system and the new script format naming the boot strings.
For example:
Installing SSM Firmware ...
****************************************************************
* CAUTION *
* *
* The VBAD Flash PROMs MUST be updated before rebooting the *
* system. The Flash PROM update procedure is described in *
* the VBAD Software Release Notes. *
* *
****************************************************************
SSM Firmware Monitor boot strings:
VBAD Flash Prom data file: "qd(0,2)ssw/fw/ssm/lvlA.rom"
.
The bootstring info is captured in
/usr/options/ssm/BOOTSTRINGS-INFO
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.
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 at a system prompt:
shutdown -y -g120 -i0
If the system is in the single-user mode, use the command init 0 to go to Level-B of the firmware.
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.
Set up the VBAD bootstring.
Make sure that the power-up monitor VBAD bootstring is set to the same path as listed in the output from the installation script. During installation, that bootstring information was also captured and saved in the file /usr/options/ssm/BOOTSTRING-INFO.
You can look at the current value of the bo bootstring by using the print command from the Level-B prompt. For example:
---> print bo
If the bootstring is different from the installation script output, you must change it to match. For example:
---> bo VBADPath=qd(0,2)ssw/fw/ssm/lvlA.rom
ATTENTION If the VBAD software is moved to a different disk or partition after initial installation, the BOOTSTRING-INFO file will not provide accurate bootstring path information for later reference.
Update the VBAD board PROMs.
ATTENTION If you put incorrect data into the Flash PROMs, the VBAD software will not initialize on the next power cycle, and the system will not boot.
At the Level-B prompt, type fprog.
Select option 2 from the menu and override the default SLIC ID in the brackets by entering the SLIC ID of the desired VBAD board.
Select option 1 from the fprog menu to update the Flash PROMs and specify a filename.
Select the the following file to program into the Flash PROM:
qd(0,2)ssw/fw/ssm/lvlA.rom
After you select the file, the system displays:
Verifying input data checksum Programming FPROM at slic address xx, 0x40000 bytes Using FPROM data file qd(0,2)ssw/fw/ssm/lvlA.rom Continue? (y/n)
If you are satisfied with the selections, type y to continue. If you want to make a change, type 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 FPROM checksum FPROM programming complete.
Update all VBAD boards in the system.
Repeat Steps 6 b and Step 6 c until all VBAD PROMs have been updated to match the SSM software version.
Quit fprog.
Exit fprog by choosing option q from the fprog menu.
Verify matching Level-A and Level-B versions.
Boot a new Level-B using the zap command to simulate a system power cycle. Stop the boot at Level-B.
At the Level-B prompt, enter config and verify that all VBAD boards in the system have matching Aver and Bver values.
If there is a mismatch, repeat Step 6 b and Step 6 c until all VBAD board PROMs have been updated.
Reboot the Operating System.
At the Level-B prompt, enter bh to boot the operating system.
A slave SSM board is a second, third, or fourth SSM-2 board that is used to control a VMEbus Expansion Unit (VEU) in S2000/4x0 and S2000/7x0 systems.
ATTENTION In the case of field replacement of a slave SSM-2 board, versions of Level-A prior to V4.7 cannot load Level-B of V4.9.2 for size reasons.
Use this procedure if a defective slave SSM-2 board has been replaced in a system that already is operating with SSM software at V4.7 or higher. The replacement board may not have a version of Level-A in its PROM sufficient to boot the new V4.9.2 Level-B.
Exception: If the installer knows that the PROMs on a replacement board already contain at least V4.7 Level-A, then the board does not need this special conditioning and may be used as it is. Proceed either with updating (flashing) the PROMs to match the system's Level-B software ( Section 1.9) or with upgrading the entire system software (Section 1.6).
If the version level of the PROMs is unknown, then, after the replacement board is installed in the system, load a Level-B into the board from a distribution medium (CD-ROM or tape) before updating (flashing) its PROMs. Use the following procedure.
Load the SSM V4.9.2 distribution medium into a bootable drive.
Bring the system to the firmware Level-A of the Power-Up Monitor.
At the Level-A prompt (->), use one of the following commands to change the ssmSlavePath bootstring to point to the distribution medium for a bootable Level-B source file:
For CD-ROM (where n stands for SCSI ID x 8), type:
-> bo ssmSlavePath=dc(n,0)ssw/fw/ssm/lvlB_4.9.2
For a DYNIX/ptx tape, type:
-> bo ssmSlavePath=tm(56,61)
For a DYNIX® V3.x tape, type:
-> bo ssmSlavePath=tm(56,61)
Verify the bootstring path by typing:
-> print bo
From Level-A, boot a new Level-B by typing:
-> bs
When the Level-B prompt (--->) appears, change the ssmSlavePath bootstring back to point to the boot file on the disk with the following command:
---> bo ssmSlavePath=wd(0,2)ssw/fw/ssm/lvlB
Verify the bootstring path by typing:
-> print bo
If the entire SSM software needs to be upgraded, go to the DYNIX/ptx procedure in Section 1.6 of these release notes and install the new system software.
Otherwise, the PROMs on the slave board can be updated (flashed) at this point with the fprog command. See Section 1.9, "Updating Replacement Board PROMs," in these release notes.
ATTENTION Always update the PROMs of the replacement board to match the Level-B system software.
A resident Level-B is a prerequisite for flashing V4.9.2 Level-A into a slave SSM-2 board's PROMs. Use this procedure to reestablish a Level-B on installed slave SSM-2 boards that failed to boot during an upgrade to V4.9.2 software (Section 1.6 of these release notes).
Bring the system to Level-A of the Power-Up Monitor.
At the Level-A prompt, use one of the following commands to change ssmSlavePath to point to the distribution medium for a bootable Level-B source file:
For CD-ROM (where n stands for SCSI ID x 8), type:
-> bo ssmSlavePath=dc(n,0)ssw/fw/ssm/lvlB_4.9.2
For a DYNIX/ptx tape, type:
-> ssmSlavePath=tm(56,61)
For a DYNIX® V3.x tape, type:
-> ssmSlavePath=tm(56,61)
Verify the bootstring path by typing:
-> print bo
From Level-A, boot a new Level-B by typing:
->bs
When the Level-B prompt (--->) appears, change the ssmSlavePath back to point to the boot file on the disk with the following command:
---> bo ssmSlavePath=wd(0,2)ssw/fw/ssm/lvlB
Verify the bootstring path by typing:
-> print bo
At this point, the PROMs can be updated (flashed). To complete the V4.9.2 upgrade installation, return to the DYNIX/ptx procedure in Section 1.6, Step 6 of these release notes.
The versions of firmware (Level-A) in the PROM of each SSM or VBAD board in the system and the system software (Level-B) on the boot disk must be the same.
When you replace an existing master or slave SSM-2 or VBAD board, update (flash) the SSM-2 or VBAD PROMs with the Level-B command fprog, using the procedure in this section.
ATTENTION A replacement slave SSM-2 or VBAD board must have resident Level-B software before its PROM can be updated by the fprog command from a V4.9.2 Level-B on a master SSM-2 board. For the case of a replacement slave board whose PROM Level-A version is unknown or less than V4.7, use the conditioning procedure in Section 1.8.1 of these release notes before using this updating procedure. Return to this update procedure after the replacement board has been conditioned.
ATTENTION In S16 and S2000/2x0 systems, UV PROMs that cannot be flashed were used on earlier SSM boards (not SSM-2s). SSM boards with these part numbers must be replaced.
To update the PROMs on later SSMs, all SSM-2s, and all VBAD boards, follow these steps:
Verify that the PROMs need updating.
Sometimes the PROMs on a replacement board will already be current and you can directly reboot the system without further changes.
Bring the system to the Level-B prompt (--->) from multiuser or single user by shutting down the operating system gracefully, or from Level-A by typing bs.
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.
Display the system configuration by typing the config command at the Level-B prompt. The configuration listings should show an Aver (SSM firmware on PROMs) and Bver (SSM software on disk) value for all SSM or VBAD boards in the system.
If all version levels match, terminate this procedure and reboot the system.
If Aver is lower than Bver for any SSM or VBAD board, go on to Step 2
ATTENTION If you put incorrect data into the Flash PROMs, the VBAD software will not initialize on the next power cycle, and the system will not boot.
Update the Flash PROMs of the master SSM board first.
ATTENTION In systems with more than one SSM-2 board, the master SSM-2 will be identified as board number 0 in the config display, and it will have the lowest SLIC ID of all SSM-2s in the system by virtue of its card-cage location. The SLIC ID of the master board will always be the default value listed in option 2 of the fprog menu.
At the Level-B prompt, type fprog.
Select option 2 from the menu. The master SSM board SLIC ID will automatically be selected as the default value.
If a slave SSM-2 or VBAD board PROM is to be updated, override the default value by entering the SLIC ID of the chosen board from the config display.
Select option 0 from the fprog menu to read the PROM type from the board. If the manufacturing code is:
Mfg. code = 0x42EB
it means that the board is an early-version SSM board with non-flashable UV PROMs that must be replaced to update the firmware. All other values of manufacturer and device codes mean that the PROM is programmable.
Select option 1 from the fprog menu to update the Flash PROMs and specify a filename.
Typically, the file to program into the Flash PROM will be one of the following:
wd(0,2)ssw/fw/ssm/lvlA16.rom (for SSM)
wd(0,2)ssw/fw/ssm/lvlA.rom (for SSM-2)
qd(0,2)ssw/fw/ssm/lvlA.rom (for VBAD)
After you select the file, the system displays:
Verifying input data checksum Programming FPROM at slic address xx, 0x40000 bytes Using FPROM data file wd(0,2)ssw/fw/ssm/lvlA16.rom Continue? (y/n)
(The data filename might be different depending on your selection.)
If you are satisfied with the selections, type y to continue. If you want to make a change, type 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 FPROM checksum FPROM programming complete.
Update any slave SSM-2 or VBAD boards.
For systems with slave SSM-2 or VBAD boards, repeat Steps 2 b through 2 d until all SSM-2 or VBAD PROMs have been updated to match the SSM software version.
Quit fprog. Exit fprog by choosing option q from the fprog menu.
Reboot the system.
The new SSM 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. Enter:
-> bs (to get to Level-B, then enter)
---> bh (to boot the operating system)
If the monAuto boot flag has been set to 1, the system will automatically come up to Level-B.
At Level-B, display the system configuration by typing the config command at the prompt. The configuration listing should show an Aver (SSM firmware on PROMs) and Bver (SSM software on disk) value for all SSM and VBAD boards in the system. If Aver and Bver do not match, you must update the PROMs, as described in Section 1.9. If the versions match, then enter:
---> bh (to boot the operating system)
If the current Level-B is corrupted, boot the system software directly from the SSM distribution medium (CD-ROM or tape):
Power-cycle the system and halt the booting process at the Level-A prompt (->) by typing any character within 5 seconds after the prompt appears.
Insert the distribution medium into a bootable drive.
Boot the SSM software using one of the following commands (where n stands for SCSI ID x 8):
For S16 and S2000/2x0 systems, type:
-> bs dc(n,0)ssw/fw/ssm/lvlB16 to boot from CD-ROM.
-> bs tm(56,1) to boot from tape.
For S2000/4x0 and S2000/7x0 systems, type:
-> bs dc(n,0)ssw/fw/ssm/lvlB to boot from CD-ROM.
-> bs tm(56,3) to boot from tape.
When the Level-B prompt (--->) appears, you can then boot either the operating system:
---> bh
or the Diagnostic Executive:
---> bs doDiags
If the current Level-B is corrupted, boot the system software directly from the distribution media (CD-ROM or tape):
Power-cycle the system and halt the booting process at the Level-A prompt (->) by typing any character within 5 seconds after the prompt appears.
Insert the distribution medium for SSM/VBAD software into a bootable drive.
At Level-A, use one of the following commands to set the VBADPath to point to the distribution media :
For CD-ROM, type:
-> bo VBADPath=qc(0x500,0)ssw/fw/ssm/lvlB
For tape, type:
-> bo tq(0x400,1)
From Level-A, boot a new VBAD Level-B by typing:
-> bs
When the Level-B prompt (--->) appears, you can then boot either the operating system:
---> bh
or the Diagnostic Executive:
---> bs doDiags
When replacing a defective boot disk (wd0) with a blank disk, perform Steps 1 through Step 4 of Section 1.10.1 of this document, with this exception:
At the Level-B prompt, load and boot a new miniroot and operating system from distribution media, as described in DYNIX/ptx System Administration Guide, Vol. 2, Chapter 19.
The cited manuals also describe how to rebuild the operating system and filesystem from backup tapes.
ATTENTION In the following examples of system output, the file sizes in bytes will vary from release to release.
To boot the diagnostics from tape while at a current Level-B prompt, type:
---> bs tm(56,6)
The system will display a message similar to the following example:
Booting intermediate loader from tape booting SSM from `tm(56,12' loading 258048 bytes booting SSM from `tm(56,6' loading 1007616 bytes
To boot the diagnostics from CD-ROM while at a current Level-B prompt, type:
---> bs dc(n,0)ssw/diag/ssm/exec
where n stands for 8 x SCSI ID of a bootable drive.
Assuming that a CD-ROM drive is installed in slot 5 of a 5.25-inch Pbay connected to an SSM SCSI port, the system will display a message similar to this example:
booting SSM from `dc(40,0)ssw/diag/ssm/ldr' loading 258048 bytes booting SSM from `dc(40,0)ssw/diag/ssm/exec' loading 1073152 bytes
ATTENTION With the release of Version 4.6, the path for diagPath was changed to add the ssm directory between the diag and exec directories. You may need to change the bootstring for diagPath.
The system will display a message similar to the following example:
---> bs wd(0,2)ssw/diag/ssm/exec
The system will display the following messages:
booting SSM from `wd(0,2)ssw/diag/ssm/ldr' loading 258048 bytes booting SSM from `wd(0,2)ssw/diag/ssm/exec' loading 1073152 bytes
This section describes known problems in Version 4.9.2 of the Diagnostic Executive, diagnostic tests, and SSM software (also called the Power-Up Monitor). Most problem reports include a way to work around the problem.
Unless otherwise stated, fixes for the problems listed here will be considered for inclusion in a future release of the product.
Occassionally, issuing the /etc/bootflags command with any of the options to display the firmware boot parameters will cause a DYNIX/ptx V4.0.x system to panic. This problem is caused by the random values in certain registers at the time the command is issued. When this problem occurs, the firmware is also disabled so that an automatic reboot following the system panic will not occur.
This problem does not occur in DYNIX/ptx V2.1.x systems because the -bh, -bs, or -bo options are not available for the /etc/bootflags command.
Workaround #1. Avoid using the -bh, -bs, or -bo options with the /etc/bootflags command on DYNIX/ptx V4.0.x systems. Instead, unsecure the system and issue Ctrl-P to go temporarily to the Level-B firmware prompt, then issue the print command with either the bh, bo, or bs arguments to view the bootpath parameters. Return to the operating system by issuing the quit command and resecure it.
Workaround #2. If the -bh, -bs, or -bo options are inadvertently issued with the /etc/bootflags command and the system crashes, the system must be hard-booted from the RESET button or powered down and then powered up.
Two of the tmb (QIC-525 Tape Drive) tests fail when the density variable has been set for QIC-120 and certain types of tapes are used.
Test tmb 1.3 fails for all tape types except DC6525 and DC6320. Tape types DC615A, DC600A, DC6037, DC6150, and DC6250 will cause this error to occur:
Error # 108 'Read Block Size Limits' Expected max block length = 0x8000 Actual max block length = 0xFFFFFF
Workaround. When running the tmb test, use a DC6525 or DC6320 tape cartridge.
Test tmb 1.6 fails regardless of the tape type. The following error message is displayed when this error occurs:
Error # 112 'Incorrect Mode data returned from the Mode Sense Command' Expected data = 0x19 Actual data = 0x1A
Workaround. When running the tmb test, ignore this error message or deselect the tmb 1.6 test.
The external loopback subtest 8.4 of the ETHER-V test eg may incorrectly report intermittent errors if it is run while the traffic level on the EthernetTM is high. This is caused by a problem in the firmware on revisions A and B of the VMEbus ETHER-V Ethernet controller boards. This problem does not occur on ETHER-V boards with revision C or later firmware.
The error messages associated with this condition are:
LANCE Loopback Packet Size Error
LANCE External Loopback Tx/Rx Timeout
In contrast, real hardware problems in the cable from the Ethernet board to the transceiver, or in the transceiver itself, will result in the same errors every time the test is run.
Workaround. Loop on the test or run multiple passes. If it fails on each loop or pass, the error reports are valid. If the test fails intermittently (passes sometimes, fails sometimes), then the errors are due to Ethernet traffic and should be disregarded.
If you abort the ½-inch SCSI tape drive's internal self-test during diagnostic tests tg 1.3 or 2.1, there is a possibility that the drive will hang. This only happens with older versions of tape drive firmware.
Workaround. Power-cycle the tape drive.
Because of the way XEROX® 4054 printers buffer incoming data while the printer is off line, subtest 5.1 of the Diagnostic Executive's Parallel Printer Port test, sp, always returns an error indicating that the printer is off line. An example of the error message is:
-<E>- 21:30:18 UTC: sp 5.1, error number 101, pass 0 -<E>- Failing unit: WP 0 on SSM 0 (slot 0, SLIC 0) -<E>- Not expected offline condition status -<E>- exp = 0x40 -<E>- act = 0xD0
Workaround. Do not use this subtest with a XEROX 4054 printer.(Subtest 5.1 is normally deselected.)
This section of the release notes contains information that will be placed in other documents at the next revision of those documents. The following information is provided here:
The bs save and bs restore commands (see Section 1.13.1)
This section contains all the information about the bs command that currently exists in the SSM/CSM Power-UP Monitor Guide, plus descriptions of the save and restore arguments.
The bs command loads the Level-B power-up monitor software or the Diagnostic Executive. The bs command also allows you to set boot flags and boot paths to boot automatically each time the system is powered up or reset.
Syntax:
bs [diagAuto [= {1,0}]] [diagPath [= bootstring]] [doDiags] [lvlBPath [= bootstring]] [lvlBTests [= bootstring]] [monAuto [= {1,0}]] [restore] [save]
Description:
ATTENTION The save and restore options work only on filesystems created under DYNIX/ptx V4.2 or later. SSM software cannot write to filesystems created under earlier operating system versions.
Entering the bs command without any options at Level-A boots the Level-B software from the path designated in lvlBPath.
Entering the bs command and an option name without specifying a value displays the current setting of that option.
Defaults
These paths will differ from one system type to another:
---> print bs
bsboot SSM or CSM firmware or the Diagnostic Executive
lvlBPath=qd(0,1)ssw/fw/csm/lvlB
monAuto=0
diagPath=qd(0,1)ssw/diag/csm/exec
diagAuto=0
lvlBTests=qd(0,1)ssw/fw/csm
Examples
For SSM systems:
---> bs diagPath = wd(0,2)ssw/diag/ssm/exec
For S5000 systems:
---> bs diagPath = qd(0,2)ssw/diag/csm/exec
---> bs lvlBTests = qd(0,2)ssw/fw/csm
---> bs save
Save boot strings to file qd(0,10)boot_str.....
For WS5000 systems:
---> bs diagPath = qd(0,1)ssw/diag/csm/exec
---> bs lvlBTests = qd(0,1)ssw/fw/csm
For any system:
---> bs monAuto = 1
Boot string data is saved in the file /usr/options/<product_name>/BOOTSTRING-INFO, where <product_name> can be ssm, csm, or qcic. You can look at the current values of the bs and bh boot strings by using the print command from the Level-B prompt.
---> print bh
ATTENTION On DYNIX/ptx systems, you can display and change bootstrings from the OS using the DYNIX/ptx bootflags command. For information, type man bootflags at the OS prompt.
During system software installation, the system displays the name of each product as it is installed and lists the path for the boot strings. If any of the boot strings do not match what is listed by the installation script, you must change them to match the output from the installation script. For example:
---> bh loaderPath=qd(0,2)ssw/boot
File Number |
Description |
0 |
INSTALL script for menu system (cpio archive) |
1 |
lvlB16 (Level-B operational firmware for S16 & S2000/2x0) |
2 |
lvlA16 (Level-A ROM image for S16 & S2000/2x0) |
3 |
lvlB (Level-B operational firmware for S2000/4x0 & S2000/7x0) |
4 |
lvlA (Level-A ROM image for S2000/4x0 & S2000/7x0) |
5 |
Place-holder file |
6 |
Diagnostic Executive |
7 |
Diagnostic Executive menu |
8 |
lvlB board test proc486test |
9 |
lvlB board test qcicTest |
10 |
lvlB board test mem2Test |
11 |
lvlB board test procpenttest |
12 |
lvlB intermediate loader ldr |
13 |
Diagnostic autoconfig |
14 |
Diagnostic autoconfig.aux |
15 |
Diagnostic probe |
16 |
Diagnostic probe.aux |
17 |
Diagnostic symmem |
18 |
Diagnostic cadm |
19 |
Diagnostic clkarb |
20 |
Diagnostic clkarb |
21 |
Diagnostic pentproc |
22 |
Diagnostic pentproc.aux |
23 |
Diagnostic mdscan |
24 |
Diagnostic mdproc |
25 |
Diagnostic mdproc.aux |
26 |
Diagnostic symproc |
27 |
Diagnostic symproc.aux |
28 |
Diagnostic multiproc |
29 |
Diagnostic multiproc.aux |
30 |
Diagnostic ssm2 |
31 |
Diagnostic vb |
32 |
Diagnostic qcic |
33 |
Diagnostic qcic.aux |
34 |
Diagnostic multiqcic |
35 |
Diagnostic multiqcic.aux |
36 |
Diagnostic dcc_ut |
37 |
Diagnostic dcc_ucode |
38 |
Diagnostic mbad |
39 |
Diagnostic sced |
40 |
Diagnostic pbay |
41 |
Diagnostic tm |
42 |
Diagnostic tma |
43 |
Diagnostic tmb |
44 |
Diagnostic tf |
45 |
Diagnostic tg |
46 |
Diagnostic ex |
47 |
Diagnostic zd |
48 |
Diagnostic xs |
49 |
Diagnostic dcp |
50 |
Diagnostic eg |
51 |
Diagnostic eg.aux |
52 |
Diagnostic per |
53 |
Diagnostic vj |
54 |
Diagnostic sd |
55 |
Diagnostic cd |
56 |
Diagnostic owl |
57 |
Diagnostic st |
58 |
Diagnostic mdcp |
59 |
Diagnostic xt |
60 |
Diagnostic sp |
61 |
V4.6.1 Level-B copy for slave SSM |
62 |
Installation scripts |
63 |
cpio of firmware levels |
64 |
cpio of diagnostics |