Version 1.6.1 of the CSM system software and Diagnostic Executive software is compatible with all CSM-based systems.
Version 1.6.1 is compatible with DYNIX/ptx on S5000 systems and with Windows NT Server on WS5000 systems. It is not compatible with DYNIX® 3.x operating systems.
ATTENTION In this document, the term " CSM system software" includes the Power-Up Monitor and the Diagnostic Executive programs.
ATTENTION Always flash the Level-A PROM when upgrading CSM software. This is especially important when upgrading from CSM V1.4.1 or earlier to CSM V1.5 or later. Serious problems can result if the Level-A and Level-B versions do not match. Beginning with CSM V1.6.0, a warning message is displayed if the Level-A and Level-B versions do not match. This situation is likely to occur when replacing a CSM board.
After correcting a mismatch, you may need to erase the NVRAM and install the factory default NVRAM settlings using the ram scrub command. Be sure to write down any customized NVRAM data before performing the scrub so that you can re-enter the data after the scrub.
Refer to Appendix A for instructions about flashing PROMs.
Version 1.6.1 includes all the functionality of Version 1.6 for S5000 and WS5000 systems plus the following new features:
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 supports DYNIX/ptx V4.4 and later.
Non-OS bootstrings must still begin with qd(0,0). (With OS versions prior to DYNIX/ptx V4.4, non-OS bootstrings must still begin with qd(0,2). 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'
When power-up tests are not run, the CSM software now automatically deconfigures an HDM board if a memory module on that board fails to initialize on power-up.
When a write to the diary RAM on a given board fails, the CSM software now displays that board's ID.
The HDM diary full message now includes the HDM board ID.
SE20/30/40 systems can now boot the operating system with one failed fan (when the other five fans are good).
Console messages during the skipMemClear operation have been improved. The new messages, which make it clear whether or not memory is being cleared, are one of the following depending on the skipMemClear flag: "Clearing memory," "Skipping clear of memory," or "Clearing memory to generate valid EDC bits."
The bh skipMemClear flag has been added to the opmode command so that skipMemClear can be selected from the OS. System administrators who have incorporated opmode access into their scripts may need to modify those scripts. See Chapter 3 for more information.
The td diagnostics test (for DDSTM -2 drives) no longer runs the erase test by default. The erase test takes a long time to run. This change reduces the default time required to run the td diagnostics test.
u is no longer accepted as an abbreviation for the umon command. To reduce the risk of users inadvertently executing the umon command, users must now type out the complete command name umon.
Starting with V1.6.1, any change to the monEntry sequence is immediately reflected in the remote port.
The installation software now generates correct bootstrings for disks with numbers greater than 9.
The daylight savings time bit in the CSM clock chip is now initialized.
In previous releases, a large number of console messages could cause the TOD (Time of Day) updates to fall behind. Starting with CSM V1.6.1, TOD updates now have a higher priority than console messages.
Support has been added for DYNIX/ptx V4.2 and later filesystems. Prior to this release, the CSM software could not write to DYNIX/ptx V4.2 or later filesystems.
Read-only support has been added for ptx/Enhanced File SystemTM (ptx/EFS) V1.2.
The pa (probe all) Diagnostics Executive command now probes for RAID devices at LUNs 0 through 3. Also, the output of the pa command now includes a field for the SCSI LUN. It is still recommended that you use the ptx/Online Diagnostics to actually test a RAID array.
Support has been added 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.
V1.6.1 corrects a problem in the CSM software that in previous releases would change the autoBoot flag from 1 to 32 during an OS panic. This bug did not cause any problems, but it did cause confusion for users.
DYNIX/ptx V4.4 flexible disk naming is now supported.
DYNIX/ptx V4.4 dumpconf format is now supported.
If your shipment is incomplete or you encounter problems while installing the system software, contact your local Customer Support representative.