AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes VAX 7000/10000 SYSTEM MODEL 600, 700, & 800 CONSOLE V4.3 RELEASE NOTES Revision/Update Information: V4.3 - Console Firmware Release Revenue Servers Engineering - VAX7000/10000 Console Group This document describes the VAX 7000/10000 Model 600, Model 700 and Model 800 console version V4.3 in terms of the differences from V4.2. AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes CHAPTER 1 INSTALLATION PROCEDURE The Laser Firmware Update utility (LFU) should be used to update the console firmware. Complete documentation on LFU and console commands can be found in the following manuals: o DEC 7000 AXP, VAX 7000 Operations Manual (order number EK- 7000B-OP) o DEC 7000 AXP, VAX 7000 System Service Manual (order number EK-7002B-SV) o DEC 7000 AXP, VAX 7000 Console Reference Manual (order number EK-70C0B-TM) LFU is an offline loadable program which is designed to update firmware on any device residing on the Laser bus or XMI bus. LFU is the only offline update utility needed on the Laser platform. In the past, an update utility was needed for each specific device residing in a system. LFU is designed to support all devices on the Laser platform while providing a common and consistent user interface to the operator. 1.1 Preparation This LFU release VAX7000_V0C (for VAX 7000/10000 Systems) is booted from the Infoserver, using the VAX 7000/10000 Console CD (order number AQ-PQW1H-BE) Installation Procedure 1 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes The steps to installing the console are: 1. Install the LFU CD on your Infoserver, or install the MOP- bootable LFU image in the MOM$SYSTEM directory of your MOP boot server node. 2. Boot LFU and follow the instructions in Section 1.4. 1.2 Saving customized parameters Later in the upgrade, in Section 1.5, the EEPROMs are rebuilt. As a result of the rebuild, all environment variables are set to their default values and all user defined environment variables are erased. Issuing a "SHOW *", at this time, will display all current (customized) settings. A copy of the "SHOW *" output will be useful later in the up- grade, in Section 1.6, if one desires to restore the system's settings to the current values. >>> show * auto_action HALT baud 9600 boot_file boot_osflags 0,0,1 boot_reset ON bootdef_dev dua214.0.0.9.0 booted_dev bootvax_compat OFF compat_mode ON cpu 0 cpu_enabled ff cpu_primary ff d_harderr halt d_report summary d_softerr continue dump_dev enable_audit ON interleave default 2 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes language 36 mopv3_boot 0 prompt >>> version V4.2-4835 Feb 19 1996 08:57:35 1.3 Booting LFU The update may be performed by booting LFU, either via the Infoserver or the MOP-bootable LFU image directly over the network. A typical example of booting each is shown below; note that the console and SROM versions may not exactly match what will appear on your console output: NOTE It is recommended to set AUTO_ACTION to HALT before run- ning LFU. 1.3.1 Booting via the Infoserver >>> boot -flags 0,0,0 exa0 -file ISL_LVAX_V07 Initializing... F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # A M . . . P P P P TYP o + . . . + + + + ST1 . . . . . E E E B BPD o + . . . + + + + ST2 . . . . . E E E B BPD + + . . . + + + + ST3 . . . . . E E E B BPD + . + . . . + . . . . . + . C0 XMI + + . . . . . + . . . . . + + C1 XMI + . . . . . . . . . . . . . . . . C2 . . . . . . . . . . . . . . . . C3 . A0 . . . . . . . ILV . 128 . . . . . . . 128MB Installation Procedure 3 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes Firmware Rev = V4.2-4835 SROM Rev = V3.1-0 SYS SN = SG210KSH79 P00>>> Booting... Connecting to boot device exa0 Created boot device: exa0.0.0.14.0 resulting file is mopdl:ISL_LVAX_V07/exa0 ..... Load complete! Image loaded at address: 00128e00 Image size: 87552 Target name: Target address: 00-00-00-00-00-00 Host name: ACHE Host address: aa-00-04-00-22-74 bootstrap code read in base = 128c00, start = 200 boot device name = exa0.0.0.14.0 boot flags 0,0,0 boot device type = 69 controller ID = a unit number = 0 node ID = 0 channel = 0 slot = 14 hose = 0 jumping to bootstrap at 128e00 Network Initial System Load Function Version 1.1 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3 4 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 1 Working Servers found:: 1 Service Name Format: Service Number Service Name Server Name Ethernet ID #1 SMC P9_ESS 08-00-2B-24-72-6B #2 6000_DIAG_H P9_ESS 08-00-2B-24-72-6B #3 VAX7000_V0C P9_ESS 08-00-2B-24-72-6B Enter a Service Number or for more: 3 Copyright Digital Equipment Corporation 1991, 1993, 1994, 1995 All Rights Reserved. Loadable Environment Rev: V4.3-4842 Sep 12 1996 10:16:10 ***** Loadable Firmware Update Utility ***** Version 13.0 17-Oct- 1995 Installation Procedure 5 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes ----------------------------------------------------------- ------------------ Function Description ----------------------------------------------------------- ------------------ Display Displays the system's configuration table. Exit Return to loadable offline operating environment. List Lists the device types and firmware revisions supported by this revision of LFU. Modify Modifies port parameters and device attributes. Show Displays device mnemonic, hardware and firmware revisions. Update Replaces current firmware with loadable data image. Verify Compares loadable and device images. ? or Help Scrolls the function table. ----------------------------------------------------------- -------------------- Function? 1.3.2 Booting via MOP LFU image >>> boot -flags 0,0,0 exa0 -file VAX7000_V0C Initializing... F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # A M . . . P P P P TYP o + . . . + + + + ST1 . . . . . E E E B BPD o + . . . + + + + ST2 . . . . . E E E B BPD + + . . . + + + + ST3 . . . . . E E E B BPD + . + . . . + . . . . . + . C0 XMI + + . . . . . + . . . . . + + C1 XMI + . . . . . . . . . . . . . . . . C2 . . . . . . . . . . . . . . . . C3 6 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes . A0 . . . . . . . ILV . 128 . . . . . . . 128MB Firmware Rev = V4.2-4835 SROM Rev = V2.0-0 SYS SN = SG210KSH79 P00>>> Booting... Connecting to boot device exa0 Created boot device: exa0.0.0.14.0 resulting file is mopdl:VAX7000_V0C/exa0 ..... Load complete! Image loaded at address: 00128e00 Image size: 3068928 Target name: Target address: 00-00-00-00-00-00 Host name: ACHE Host address: aa-00-04-00-22-74 bootstrap code read in base = 128e00, start = 000 boot device name = exa0.0.0.14.0 boot flags 0,0,0 boot device type = 69 controller ID = a unit number = 0 node ID = 0 channel = 0 slot = 14 hose = 0 jumping to bootstrap at 128e00 Copyright Digital Equipment Corporation 1991, 1993, 1994, 1995 All Rights Reserved. Loadable Environment Rev: V4.3-4842 Sep 12 1996 10:16:10 ***** Loadable Firmware Update Utility ***** Version 13.0 17-Oct- 1995 Installation Procedure 7 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes ----------------------------------------------------------- ------------------ Function Description ----------------------------------------------------------- ------------------ Display Displays the system's configuration table. Exit Return to loadable offline operating environment. List Lists the device types and firmware revisions supported by this revision of LFU. Modify Modifies port parameters and device attributes. Show Displays device mnemonic, hardware and firmware revisions. Update Replaces current firmware with loadable data image. Verify Compares loadable and device images. ? or Help Scrolls the function table. ----------------------------------------------------------- -------------------- Function? 1.4 Updating the firmware After booting the LFU as in the previous section, select one of the LFU options. This example shows updating the console and all the adapter firmware. Function? update all Name Type Rev Mnemonic FW Rev HW Rev LSB 0+ KA7AA (8002) 0006 ka7aa0 F 1+ KA7AA (8002) 0006 ka7aa0 F 7+ MS7AA (4000) 0000 ms7aa0 8+ IOP (2000) 0002 iop0 8 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes C1 XMI xmi0 2+ KFMSA (0810) A4A6 kfmsa0 5.6 A04 8+ DWLMA (102A) 0003 dwlma0 C+ KDM70 (0C22) 1E01 kdm700 3.0 E+ DEMNA (0C03) 0802 demna0 8.2 C3 XMI xmi1 1+ DEMFA (0823) 91FF demfa0 15.15 2+ KFMSA (0810) A4A6 kfmsa1 5.6 A04 8+ DWLMA (102A) 0104 dwlma1 E+ CIXCD (0C05) 4611 cixcd0 70.0 A01 Update ALL devices? [Y/(N)] Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! ka7aa0 Updating to 4.3... Reading Device... Verifying 4.3... PASSED. WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! ka7aa1 Updating to 4.3... Reading Device... Verifying 4.3... PASSED. ms7aa0 not supported under LFU. iop0 not supported under LFU. kfmsa0 firmware rev is greater or equal to update rev. Continue? [Y/(N)] N kfmsa1 firmware rev is greater or equal to update rev. Continue? [Y/(N)] N dwlma0 not supported under LFU. dwlma1 not supported under LFU. WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! kdm700 Updating to 4.4... Reading Device... Verifying 4.4... PASSED. WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! demna0 Updating to 9.4... Reading Device... Verifying 9.4... PASSED. demfa0 firmware rev is greater or equal to update rev. Continue? [Y/(N)] N Installation Procedure 9 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes cixcd0 firmware rev is greater or equal to update rev. Continue? [Y/(N)] N Function? EXIT Initializing... F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # A M . . . . . P P TYP o + . . . . . + + ST1 . . . . . . . E B BPD o + . . . . . + + ST2 . . . . . . . E B BPD + + . . . . . + + ST3 . . . . . . . E B BPD . . . . . . . . . . . . . . . . C0 + . + . . . + . . . . . + . C1 XMI + . . . . . . . . . . . . . . . . C2 + . . . . . + . . . . . + + C3 XMI + . A0 . . . . . . . ILV . 128 . . . . . . . 128MB Firmware Rev = V4.3-4842 SROM Rev = V3.1-0 SYS SN = SG01234567 CPU:0 EEPROM Image is incorrect version CPU:1 EEPROM Image is incorrect version System configuration has changed since last saved configuration! >>> 1.5 Updating Console Data Structures The format of the EEPROM was changed in V3.0. If upgrading from an older version of console, the EEPROM on each cpu module MUST be reinitialized with the "BUILD EEPROM" command. A new saved configuration MUST be made with the "SET CONFIG" command. Also, a new console data structure MUST be initialized with the "BUILD NVR" command. It is recommended that these steps be followed for ALL console upgrades. 10 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes As a result of the "BUILD EEPROM", the console terminal baud rate is set to 9600 baud. Example: P00>>> build nvr P00>>> build eeprom Create new EEPROM image [Y/(N)]? y Creating new EEPROM Image P00>>> set cpu 1 P01>>> build nvr P01>>> build eeprom Create new EEPROM image [Y/(N)]? y Creating new EEPROM Image P01>>> set cpu 0 P00>>> set config P00>>> # P00>>> # NOTE: Your terminal baud rate is reset to the default value, 9600, P00>>> # during the BUILD EEPROM process. Although the SHOW BAUD still P00>>> # displays your previous setting, a SET BAUD [previous_value] must P00>>> # be executed to retain your desired baud rate. For example: P00>>> sho baud baud 2400 P00>>> set baud 2400 baud set to 2400 P00>>> With V3.0 and later upgrades, the serial EEPROMs on the MS7AA's, the IOP and the DWLMA's must be initialized using the BUILD SEEPROM command. If it is the first time the serial EEPROMs are being built, the command will prompt for the module serial number, the module part number and the module firmware revision. The serial number and the module part number can be found on the yellow label on the module. These modules have no firmware so this question can be answered with any value. Installation Procedure 11 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes Example: P00>>> P00>>> build seeprom * Create new serial EEPROM image for ms7aa0 [Y/(N)]? y Creating new serial EEPROM image for ms7aa0 Module Serial Number> sg1234567 Module Unified 2-5-2.4 Part Number> 20-E2043-AA.0000 Module Firmware Revision> xx please wait ~1 min, writing ms7aa0 Create new serial EEPROM image for iop0 [Y/(N)]? y Creating new serial EEPROM image for iop0 Module Serial Number> sg1234567 Module Unified 2-5-2.4 Part Number> 20-E2044-AA.0000 Module Firmware Revision> xx please wait ~1 min, writing iop0 Create new serial EEPROM image for dwlma0 [Y/(N)]? y Creating new serial EEPROM image for dwlma0 Module Serial Number> sg1234567 Module Unified 2-5-2.4 Part Number> 20-T2028-AA.0000 Module Firmware Revision> xx please wait ~1 min, writing dwlma0 Create new serial EEPROM image for dwlma1 [Y/(N)]? y Creating new serial EEPROM image for dwlma1 Module Serial Number> sg1234567 Module Unified 2-5-2.4 Part Number> 20-T2028-AA.0000 Module Firmware Revision> xx please wait ~1 min, writing dwlma1 P00>>> 12 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes 1.6 Restoring customized parameters To restore the customized system parameters to what they were before the console firmware upgrade, refer to the parameters saved in the section, SAVING CUSTOMIZED PARAMETERS. The "SHOW *" display in that section should be compared with the "SHOW *" issued in this section. In this example, the value to restore is bootdef_dev. P00>>> show * auto_action HALT baud 9600 boot_dev boot_reset ON bootdef_dev booted_dev bootvax_compat OFF compat_mode ON cpu 0 cpu_enabled ff cpu_primary ff d_dskloop normal d_harderr halt d_netloop external d_report summary d_softerr continue dump_dev enable_audit ON interleave default language 36 prompt >>> system_variant 0 version V4.3-4842 Aug 19 1996 15:59:21 P00>>> P00>>> set bootdef_dev dua214.0.0.9.0 bootdef_dev set to dua214.0.0.9.0 P00>>> init Installation Procedure 13 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes Initializing... 1.7 LFU Release V0C The LFU release VAX7000_V0C is for the VAX7000/10000 and sup- ports the devices listed below. In the future, support will be added for additional devices if necessary. Both the LFU program and the firmware microcode images it writes are supplied on a CD-ROM. This release of LFU includes the following revisions: ________________________________________________________________ type__________name__________mnemonic______hardware_________firmware 0C05 CIXCD cixcd All Revs 72.0 0823 DEMFA demfa All Revs 2.1 0C03 DEMNA demna All Revs 9.4 8002 KA7AA ka7aa All Revs 4.3 8007 KA7AB ka7ab All Revs 4.3 8008 KA7AC ka7ac All Revs 4.3 0C22 KCM44 kcm44 All Revs 3.1 0C22 KDM70 kdm70 All Revs 4.4 0810 KFMSA kfmsa A01 - A255 5.10 0810__________KFMSA_________kfmsa_________B01_-_B04________5.6__ 14 Installation Procedure AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes CHAPTER 2 QUICK GUIDE TO BOOTING This section describes the minimum amount of information you need to boot a system with console V4.3. 2.1 Knowing your disk device name The long form of the disk device name is recommended for all situations. Once the user knows the name of the boot disk, then booting can be achieved with a single boot command. To view the console form of the name for the disks, type the console command: >>> show device This command sizes the system and finds the disk devices. It varies in speed, depending on how many I/O adapters and disks are part of the configuration. But once you have determined the name of the disk you wish to boot, then you no longer need to issue the "show device" command. 2.2 The boot command Suppose your disk is named: dua2.4.1.2.0 Quick guide to booting 15 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes This is the name supplied to the boot command. In prior releases it was common to use the disk abbreviation (eg. dua2). But the prefered practiced rule is to use the long form of the device name. >>> b dua2.4.1.2.0 NOTE Although there is limited support for abbreviations of boot device names, the full boot device name must be spec- ified for CI devices. If you boot from the same boot device each time, then you can store your disk name in an environment variable: >>> set bootdef_dev dua2.4.1.2.0 This will allow a simple single character boot command to work. >>> b 16 Quick guide to booting AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes CHAPTER 3 NEW FEATURES This section lists all new features added in recent releases: o The CDP command now works in diagnostic mode only. o The environment variable COMPAT_MODE was implemented in Version 4.2 of the VAX7000/10000 console to allow running VAX VMS Version 5.5-2 on the VAX7000/10000 Model 800 CPU. COMPAT_ MODE has three states which should be used as follows: - ON (default) - for use with VAX VMS V6.1, V6.2, V7.0 on all CPUs - OFF - for use with future releases of VAX VMS - V55 - for use with VAX VMS V5.5-2 on the Model 800 CPU The Model 600 fully supports VAX VMS V5.5-2, V6.1, V6.2, and V7.0 regardless of the setting of COMPAT_MODE. With COMPAT_MODE set to ON (default) the Model 700 supports running VAX VMS V6.1, V6.2 and V7.0. This CPU does not sup- port running VAX VMS V5.5-2. With COMPAT_MODE set to ON (default) the Model 800 supports running VAX VMS V6.1, V6.2. and V7.0. These versions of the operating system will see the CPU as a Model 700. With COMPAT_MODE set to V55, VAX VMS V5.5-2 is supported on the Model 800, but the operating system will see the CPU as a Model 600 and all restrictions pertaining to running VAX VMS V5.5-2 on a Model 600 CPU will apply (i.e., 512Mb memory limit, no BI support, etc.). New Features 17 AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes o The environment variable BOOTVAX_COMPAT was added to V4.2 of the console. It has two states: - OFF (default) - ON With BOOTVAX_COMPAT set to OFF, all reboots will occur on the initial boot device, regardless of the BOOTDEF_DEV setting. With BOOTVAX_COMPAT set to ON, all reboots will be from the device specified by BOOTDEF_DEV, regardless of the initial boot device. o Console support for installing two 2GB LSB memory modules. Only a total of 3.5GB will be configured for use by the operating system (a VAX architectural restriction). This allows a configuration that includes maximum CPUs (6) and maximum memory (3.5GB). o Support for autobooting controller-based (Phase 1) shadowed system disks. The environment variable BOOTDEF_DEV can be set to include a DSAxx device. o Support for all DSSI solid-state (EFxx) disk drives. o Support for examining extended virtual addressing (>>> exam- ine vmem:c0000000). o The granularity of bad spot checking has been enhanced so that bad spots can be found in the upper longwords of memory reads. o Booting support for disk units over 4GB in size (large drives, stripe sets and RAID sets). o Specifying an alternate HSC when booting a system disk. If the system disk was dual-pathed between two HSC-type controllers, and a failover between the controllers occured while OpenVMS/VAX was running, and the path over which the operating system was originally booted was not available upon the system shutdown (or crash), the console could not access the system disk to complete its actions. A new non-volatile environment variable (BOOT_ALT, created by the operator) 18 New Features AA-PQW2H-TE VAX7000/10000 Firmware V4.3 Release Notes allows the operator to specify the alternate path to the system disk for the console to use during shutdown in the event of a path failover. o Full support for HSJ-40, HSD-05, HSD-30 storage controllers. (CDP command support for HSD-05 does not include an initial- ization after parameter modifications.) New Features 19 AA-PQW2H-TE VAX7000/10000 Firmware V4.2 Release Notes CHAPTER 4 BUG FIXES AND ENHANCEMENTS Version 4.3 of the console contains the following bug fixes and enhancements: o A problem in which the TEST command would fail on SDI (Stan- dard Disk Interface) devices (dua*, dub*, etc.) has been fixed. This section lists all bug fixes and enhancements in recent releases. o A problem with SHOW DEVICE that caused some devices not to be listed has been corrected. o SHOW POWER now works on all CPU models. o To correct a problem with memory exhaustion, V4.2 of the console requires that the CDP and SET HOST DUP commands be used in diagnostic mode only. Previously, a SHOW DEVICE was required prior to the CDP command. Since SHOW DEVICE does not work in diagnostic mode a CONFIG command should be executed first: >>> set mode diag >>> config [adaptor-mnemonic] >>> cdp Bug Fixes and Enhancements 21 AA-PQW2H-TE VAX7000/10000 Firmware V4.2 Release Notes o CIXCD/KFMSA fixes: A problem with CIXCD retry timeouts has been corrected. One symptom of this problem is that the system would appear to hang when attempting to boot from illegal or non-existent devices. New controller types (HSJ40, HSD30, HSD05) now supported. Single path operation works under most conditions (see below). Long controller startup time (HSC95) is no longer a problem. VC connection retry improves "SHOW DEVICE" and "BOOT". DSSI controllers that have multiple devices (HSD30, HSD05) now show both disks and tapes. Reset DQI during "SHOW DEVICE" and "BOOT". This makes sure the console can find each controller. Fixed "CDP" command to skip old HSD05 firware and not to hang. o During a console boot, a bad spot found in memory during the building of the bitmap, will no longer cause the console to hang. o The "SET HOST" command problem has been fixed. This problem was found when trying to run ROM-Based Diagnostics (RBDs) on XMI adapters. o The console code will set the OH (operator halt) bit in the HWRPB Per-CPU slot upon console entry and clear it at console egress. o The console code will set the appropriate HALTCODE in the HWRPB Per-CPU slot upon console entry. o The console code will set the CEEN (CRD enable) bit prior to booting an operating system. o The problem with VAX7000/10000 Model 700 systems intermit- tently failing power-up self-test on certain configurations which included a large number of CPUs (typically four or more) when running console V1.0 has been fixed. o The TEST command now provides loopback support for network testing. However, only MOP loopback mode is currently sup- ported. MOP loopback requires a live network connection for each network device. Note: the current revision of DEMFA microcode does not support MOP loopback. 22 Bug Fixes and Enhancements AA-PQW2H-TE VAX7000/10000 Firmware V4.2 Release Notes When running in Manufacturing mode (D_GROUP set to MFG), an EV can be created to designate which CI disk should be tested. All other CI disks will not be tested when D_CI_DISK exists. To use: >>> set mode advanced >>> set d_group mfg >>> create d_ci_disk >>> test Bug Fixes and Enhancements 23 AA-PQW2H-TE VAX7000/10000 Firmware V4.2 Release Notes CHAPTER 5 KNOWN BUGS AND IDIOSYNCRASIES o The building of the console bitmap on power up was designed such that bad memory would always be put at the end of the interleave set and never be interleaved. A hardware restric- tion was found that would not allow this to work because of having to align memory on certain boundries. We have included a script file that will run on power up which will look at the results of the built in self test (BIST) and if there was a memory failure found, the interleave set will be forced to NONE. This is required so that bad memory spots can be identified since there is a high probability that they won't be found if the bad memory is interleaved with the good. To return to interleaving will require that the defective memory be fixed or replaced. A future release will address the prob- lem of identifying bad memory spots when both bad and good memory modules are interleaved together. o Support for the CIXCD does not include support for keeping track of "pathstatus". This means that if there is a bad CI path, there is a small probability that a system will not boot on the first try. A second attempt should succeed. Once the booting has read in the first block the rest of the boot will complete successfully. o The OpenVMS VAX error formatter calls the VAX 7000 Model 700 and 800 CPUs a KA7AA rather than their proper names (KA7AB and KA7AC). Known Bugs and Idiosyncrasies 25 AA-PQW2H-TE VAX7000/10000 Firmware V4.2 Release Notes o In a multiprocessor system all cpus must be running the same version of the console. Different console versions should not be mixed in a multiprocessor system. o The BOOT_RESET environment variable is only allowed to be "ON". o The console is unable to create and display a very large list of devices (disks and tapes) in response to the SHOW DEVICE command. The limit is approximately 300 devices. o The environment variable BOOTDEF_DEV supports a maximum of four device names in a boot device list. o The following TEST command features are not supported: - The -WRITE & -NOWRITE qualifiers are not currently sup- ported. - The -OMIT qualifier is not supported. - The TEST command does not currently always support D_ HARDERR. In the case where multiple exercisers are run concurrently, a halt-on-error condition will abort the failing diagnostic, but will not necessarily abort the other running exercisers. However, ^C can be used to abort further testing. o When running the TEST command, a live network should be present for network exercising. If a live network is not present, the following message will be printed, and all NET_ EX processes will be killed: Transmit failed - loss of carrier. o A problem has been found where the XBI+ and XBIB modules indicate failure (red LED on) but the console map display indicates passing modules. The problem was discovered when using a VAXBI backplane that was improperly assembled without its bus termination. The failure of the XBI module is noted upon booting VMS. This problem will be fixed in a future release of the console code. 26 Known Bugs and Idiosyncrasies