Compaq VAX 7000 Guía de instalación Pagina 45

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 50
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 44
+ Enter AXP boot file : dka100:[VMS$COMMON.SYSEXE]APB.EXE
The above will put the required good stuff in block 0 of the system disk. However, you will
notice that OpenVMS has to be up, which could be a bit of a problem if you can’t boot the
system disk! If the problem is not spotted until the system/cluster is all down, one of the
following options may be your only hope:
a. Boot Standalone Backup (from a CD).
b. Load VMB from tape, and then patch registers to boot the system disk (see STARS
article "How to load VMB from a TF85").
c. Move the disk drive to another system.
And then run WRITEBOOT from there.
14.2.6 Mandatory Patch for Cache ECC Errors on VAX7000/10000
The Cache error correction routine for the VAX 7000 and VAX 10000 does not properly
correct cache single bit errors. Temporary fix is to install one of the following patches:
VAXSYSL13_U2055 for VAX/VMS V5.5-2
VAXSYSL01_060 for OpenVMS VAX V6.0
These patches are in "Mandatory Cache ECC Error Handling Kit", CD-ROM part number
AG-PZLBA-BE, and in TIMA. To check if patch is already installed:
$ ANALYZE/SYSTEM
SDA> SHOW SYSLOA
Verify that:
MCHECK1701: X-13A2 (for VAX/VMS V5.5-2)
MCHECK1701: X-16A1 (OpenVMS VAX V6.0)
Note that if customer upgrades VMS from V5.5-2 to V6.0, the old patch will be lost and the
new will have to be installed.
The permanent fix is to do FCO 7xxx-F004.
14.2.7 SCSI Disks and Volume Shadowing with OpenVMS AXP 1.5
SCSI devices connected locally to the same AXP host, should not be included in the same
shadowset. This can cause bugchecks and "other" failures. Fixed in next release, expected
Spring ’94.
14.2.8 OpenVMS VAX V6.1 Power messages at Boot time on VAX 7000
At boot time we now check power on the 7000 and 10000 platforms. There is a problem
in the V6.1 SYSLOA code for VAX 7000 that causes the following error messages, falsely
indicating a power regulator problem.
%POWER-E-BAD, bad R0=00003003 from CTSR$GETC
%POWER-I-NOTIFY, central cabinet regulator A event, check errorlog
%POWER-E-BAD, bad R0=00003003 from CTSR$GETC
%POWER-I-NOTIFY, central cabinet regulator B event, check errorlog
These message may repeat several times. There is nothing wrong with the power. Engi-
neering will produce a patch "soon".
45
Vista de pagina 44
1 2 ... 40 41 42 43 44 45 46 47 48 49 50

Comentarios a estos manuales

Sin comentarios