_ FCO 9XXX-O003, Rev B, Keep alive failures, CCSQ MCA fix ______________________________________________________________________________ | DIGITAL FCO CATEGORY PAGE 1 | | [O] OF 11 | |______________________________________________________________________________| | FIELD CHANGE ORDER NUMBER: 9XXX-O003 | |______________________________________________________________________________| | APPLICABILITY: This "O" coded FCO replaces the P1009 VAP MCU on all VAX | | 9000-XXX systems. All field spares should also be upgraded at this time. | | | |______________________________________________________________________________| | PROBLEM & SYMPTOM: 1. Keep Alive Failures due to TB Arbitration. 2. Varying | | symptoms due to the wrong cache set being selected after delayed PTE write | | into TB. 3. SBE and DBE during cache writebacks invoked via ERROR_SWEEP | | signal from EBOX. | |______________________________________________________________________________| | SOLUTION: The fix is to the CCSQ MCA | |______________________________________________________________________________| | QUICK CHECK: Insure that P1009 is at revision "L02". | |______________________________________________________________________________| | PRE/COREQUISITE FCO: N/A | MTTI HRS | | | 3 hrs. | |___________________________________________________________________|__________| | TOOL/TEST EQUIPMENT: | | EK-KA901-MG VAX 9000 System Maintenance Guide, Vol 1 | | VAX 9000 Connector Torque Tool Kit (p/n 29-28230-01) | |______________________________________________________________________________| | FCO PARTS INFORMATION | |______________________________________________________________________________| | FCO KIT NO. | DESCRIPTION OF CONTENTS | EQ KIT VARIATION | |______________|____________________________________________| APPLICABILITY | | EQ-01610-01 | P1009-AA VAP MCU, Rev. L02 | | | EQ-01610-02 | AQ-A5491-JS B6 VAP Software Update Tape | N/A | | FA-04942-01 | FCO Document | | |______________|____________________________________________|__________________| | FCO CHARGING INFORMATION | |______________________________________________________________________________| | WARRANTY/CONTRACT || NONWARRANTY/NONCONTRACT | |___________________________||_________________________________________________| | ON-SITE | OFF-SITE || ON-SITE | OFF-SITE | MATERIAL ONLY | |_____________|_____________||_____________|_____________|_____________________| |TRAVEL/| EQ | | EQ ||TRAVEL/| EQ | | EQ |ORDER-ADMIN,HANDLING | |INSTALL| KIT |INSTALL| KIT ||INSTALL| KIT |INSTALL| KIT |PKG,SHIPPING & EQ KIT| |_______|_____|_______|_____||_______|_____|_______|_____|_____________________| |DEC | DEC | DEC | DEC || N/A | N/A | N/A | N/A | N/A | |_______|_____|_______|_____||_______|_____|_______|_____|_____________________| | APPROVALS | |______________________________________________________________________________| | CSSE | FSHQ LOGISTICS | FS PRODUCT SAFETY | | Tom Krehel | Dick Joseph | Robert Brister | |___________________|____________________________|_____________________________| | CSSE MANAGER |This document is published | FCO RELEASE DATE | | Dino Genova |on multiple media including | 3 May 1991 | |___________________|hardcopy, Customer Services |_____________________________| | MICROMEDIA |Microfiche Libraries, | FCO REVISION | | Diane MacDonald |Customer Services CD-ROM and| B | |___________________|MDS Microfiche Libraries. |_____________________________| | POPULATION |It is also available | PARTS AVAILABILITY | | 398 |electronically via TIMA. | April, 1991 | |___________________|____________________________|_____________________________| _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 2 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ The B6 VAP software update may be copied via the ENET. Refer to the Corporate Implementation Plan (CIP) for instructions. Related Documents: ----------------- MRCSSE::NONAME:[PUBLIC]VAX9000_BUGLIST.PS VAX9000 "BUG" list Minimum revisions: ----------------- CPU: B5 VMS: V5.4A for VAX 900-210 and VAX 9000-410 V5.4-1 for VAX 9000-420/430/440 SPU: BL12 General Comments: ---------------- This document contains many procedures and these procedures require steps to be performed in specific sequences to be successful. Please take the time to review and understand this document before attempting to install this FCO. This FCO requires 3 hours for installation on a single CPU. In addition to this time, 6 hours of UETP are recommended prior to returning the system to the customer. If more than one CPU will be upgraded during the same system outage, 1 hour of UETP is recommended between CPU upgrades. Console software requirements: ----------------------------- This FCO requires BL12 console software. If the console is not at BL12, you must upgrade the console software before this FCO is installed. It is recommended that the console software upgrade be performed independent of the B6 VAP FCO. _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 3 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ VAX 9000 420/430/440 configurations: ----------------------------------- In multiple CPU kernels, VAX 9000-420/430/440, it is strongly recommended that this FCO be implemented in phases. Install the FCO in one of the CPUs by following the procedures outlined below. After each CPU has been upgraded and tested, the machine can either be returned to the customer for normal production use, or the FCO can be continued on the next CPU in the kernel. Each CPU upgrade should be tested fully as outlined in the procedure before the next CPU is upgraded. Steps 1-4 in this FCO need to be done only once for the first CPU to be upgraded. Each subsequent CPU upgrade can be accomplished by starting at step 5 in the procedure below. Update Notes: ------------ As of this release of the SCAN Pattern data files (ie, SPDI files) the SPU will no longer support the /MCU=mmm qualifier on the TEST command. When these new SPDI files are used with BL12 (or earlier) SPU software the /MCU=mmm qualifier will be accepted by the TEST command, but the desired testing will not be performed. In future releases of SPU software the /MCU=mmm qualifier will not be accepted. The only valid TEST options are /CPU=nnn and /SCU. Installation procedure: ---------------------- 1. Create [B6] and [INSTALL] directories on the SPU's RD54. First verify that these directories do not already exist. >>>DIR [000000]*.DIR If INSTALL.DIR;1 and B6.DIR;1 do not appear you must create them with the following command(s): >>>CREATE/DIRECTORY [B6] >>>CREATE/DIRECTORY [INSTALL] 2. Install the new B6 software in the [B6] directory. Load the BL12/B6 (AQ-A5491-JS) update tape into the TK50 drive and execute the following commands: >>>SET COMMAND [SYSEXE]BACKUP >>>MOUNT MUA7: * >>>BACKUP/LOG MUA7:[]KITINSTALL.CMD DUA50:[INSTALL]KITINSTALL.CMD >>>@[INSTALL]KITINSTALL _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 4 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ KITINSTALL will take approximately 20 minutes to finish >>>DISMOUNT MUA7: The following files should now be loaded into the [B6] directory: Directory DUA50:[B6] AQUARIUS.LOD;1 AQUARIUS.SYN;1 B3_SCU.CDB;1 B6_CPU.CDB;1 B_AAD_SCU01_9011160920.SPDF;1 B_AAD_SCU02_9011160940.SPDF;1 B_AAN_SCU01_9011161000.SPDF;1 C_0AD_ZFX01_9101051110.SPDF;1 C_0AD_ZFX02_9101062238.SPDF;1 C_0AN_ZFX01_9101062137.SPDF;1 C_1AD_ZFX01_9101071110.SPDF;1 C_1AD_ZFX02_9101072324.SPDF;1 C_1AN_ZFX01_9101080612.SPDF;1 C_2AD_ZFX01_9101110137.SPDF;1 C_2AD_ZFX02_9101042141.SPDF;1 C_3AD_ZFX01_9101181002.SPDF;1 C_3AD_ZFX02_9101092126.SPDF;1 C_AAA_CPU01_9101150729.SPDF;1 C_AAA_CPU02_9101180200.SPDF;1 C_AAA_CPU03_9101032101.SPDF;1 C_AAA_CPU04_9101200410.SPDF;1 C_AAA_CPU05_9011151655.SPDF;1 C_AAA_CPU06_9101071406.SPDF;1 C_AAA_CPU07_9101071946.SPDF;1 C_AAA_CPU08_9101051919.SPDF;1 C_AAA_CPU09_9101191255.SPDF;1 C_AAA_CPU10_9101082320.SPDF;1 C_AAA_CPU11_9101010717.SPDF;1 C_AAA_CPU12_9101031957.SPDF;1 C_AVA_VBX01_9101022315.SPDF;1 C_AVA_VBX02_9101040403.SPDF;1 C_AVA_VBX03_9101012045.SPDF;1 C_AVA_VBX04_9011152355.SPDF;1 C_AVA_VBX05_9011160025.SPDF;1 C_AVA_VBX06_9011160055.SPDF;1 C_AVA_VBX07_9101050843.SPDF;1 C_EDKDLJFJEHDFKFFH_DFEEFE.SPDI;1 C_EDKDLJHJEHDFKFFH_DFEEFE.SPDI;1 C_EEKDLJFJEHDFKFFH_DFEEFE.SPDI;1 C_EEKDLJHJEHDFKFFH_DFEEFE.SPDI;1 C_FDKDLJFJEHDFKFFH_DFEEFE.SPDI;1 C_FDKDLJHJEHDFKFFH_DFEEFE.SPDI;1 _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 5 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ C_FEKDLJFJEHDFKFFH_DFEEFE.SPDI;1 C_FEKDLJHJEHDFKFFH_DFEEFE.SPDI;1 FRAM.LOD;1 FRAM_NO_VBOX.LOD;1 INIT.CMD;1 IO.CMD;1 JCODE.LOD;1 LWCODE.LOD;1 SCUHIST.DAT;1 SITEINIT.CMD;1 SITESPECIFIC.CMD;1 Total of 53 files. 3. Copy the new SPDF, SPDI, and CDB files into the appropriate directories. >>>COPY [B6]*.SPD* [SYSMAINT]*/LOG >>>COPY [B6]*.CDB [UCODE]*/LOG 4. Before replacing the VAP MCU, the following tests should be executed to ensure the proper execution of the tests that will be used to verify the functionality of the new VAP MCU: Where "n" is the CPU in which the new VAP MCU will be installed: >>>SENSE CPU n >>>SHOW CONFIG/RINGS/CPU:n (Verify that no mismatches occur) >>>TEST/SCAN/LOG/TRACE/ISOLATION/CPU:n >>>SET CLOCK/SCU/CPU:ALL OFF >>>TEST/SCU/CPU:n >>>TEST/STRUCTURE/ALL/LOG/CPU:n >>>I/K >>>@[TOOLS]CPUn_ZFLEX >>>I/K >>>SET BOOTSET/PRIMARY=n >>>LOAD [SYSMAINT]EVKAA >>>ST 200 >>>^P >>>HALT/CPU:ALL >>>I/K/B >>>@[CONSOLE]CLEAR_MEMORY >>>SET BOOTSET/PRIMARY=n _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 6 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ Load VDS and run the following MACRO level Diagnostics: EVKAQ EVKAR EVKAS EVKAT EVKAU EVKAV EWKAX EWKMP DS> EXIT >>>HALT/CPU:ALL >>> 5. Proceed to step 8 if one or more CPUs in the kernel have already been upgraded to B6. Rename SITEINIT.CMD and SITESPECIFIC.CMD >>>RENAME [SYSEXE]SITESPECIFIC.CMD [SYSEXE]B5_SITESPECIFIC.CMD >>>RENAME [SYSEXE]SITEINIT.CMD [SYSEXE]B5_SITEINIT.CMD 6. Copy the new SITESPECIFIC.CMD and SITEINIT.CMD files from the [B6] directory to the [SYSEXE] directory. This command will also copy new IO.CMD and INIT.CMD files to [SYSEXE]. >>>COPY [B6]*.CMD [SYSEXE]*/LOG 7. Edit [SYSEXE]SITESPECIFIC.CMD Change the configuration masks in [SYSEXE]SITESPECIFIC.CMD so that they match the hardware configuration. Refer to [SYSEXE]B5_SITESPECIFIC.CMD for the correct values. Do not modify CDB$DEFAULT, SYS$CPU_REVISION, SYS$SCU_REVISION, or SYS$KERNEL_REVISION. These reflect changes that are necessary for the B6 update. Continue with the edits in step 8 if you are upgrading a multi CPU kernel (VAX 9000 model 420, 430, or 440). 8. Edit [SYSEXE]SITESPECIFIC.CMD Proceed to step 9 if this is a uni processor kernel (VAX 9000 model 210 and 410). _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 7 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ The new SITESPECIFIC.CMD file distributed with this update allows you to specify the CDB revision for each CPU in the configuration independently. It also allows you to define the CDB revision for all CPUs in a single command when all CPUs are at the same revision level. After you have completed the FCO on this CPU, the CDB revision must be defined for each CPU independently if you will be mixing B5 and B6 CPUs in the same kernel. If you are about to install the B6 VAP FCO in the last CPU in the kernel, and all CPUs will then be at revision B6, you can define the CDB revision for all CPUs using one line in SITESPECIFIC.CMD. Here are the defaults from the update tape which will work only if all CPUs are at revision B6 (note that the per CPU definitions are commented out): !DEFINE/SYSTEM CDB$DEFAULT_CPU0 B6_CPU.CDB ! CDB for CPU0 !DEFINE/SYSTEM CDB$DEFAULT_CPU1 B6_CPU.CDB ! CDB for CPU1 !DEFINE/SYSTEM CDB$DEFAULT_CPU2 B6_CPU.CDB ! CDB for CPU2 !DEFINE/SYSTEM CDB$DEFAULT_CPU3 B6_CPU.CDB ! CDB for CPU3 DEFINE/SYSTEM CDB$DEFAULT_CPU B6_CPU.CDB ! CDB for all CPUs DEFINE/SYSTEM CDB$DEFAULT_SCU B3_SCU.CDB ! CDB for SCU DEFINE/SYSTEM SYS$CPU_REVISION B6 ! Revision of CPU DEFINE/SYSTEM SYS$SCU_REVISION B3 ! Revision of SCU DEFINE/SYSTEM SYS$KERNEL_REVISION C ! Revision of kernel If CPU0 is a B6 CPU and CPU1 is a B5 CPU, SITESPECIFIC.CMD would look like this (note that the CDB for all CPUs is commented out along with CPUs not present): DEFINE/SYSTEM CDB$DEFAULT_CPU0 B6_CPU.CDB ! CDB for CPU0 DEFINE/SYSTEM CDB$DEFAULT_CPU1 B5_CPU.CDB ! CDB for CPU1 !DEFINE/SYSTEM CDB$DEFAULT_CPU2 B6_CPU.CDB ! CDB for CPU2 !DEFINE/SYSTEM CDB$DEFAULT_CPU3 B6_CPU.CDB ! CDB for CPU3 !DEFINE/SYSTEM CDB$DEFAULT_CPU B6_CPU.CDB ! CDB for all CPUs DEFINE/SYSTEM CDB$DEFAULT_SCU B3_SCU.CDB ! CDB for SCU DEFINE/SYSTEM SYS$CPU_REVISION B6 ! Revision of CPU DEFINE/SYSTEM SYS$SCU_REVISION B3 ! Revision of SCU DEFINE/SYSTEM SYS$KERNEL_REVISION C ! Revision of kernel CPU REV here | DEFINE/SYSTEM CDB$DEFAULT_CPU0 B6_CPU.CDB ! CDB for CPU0 ^ | CPU # here _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 8 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ NOTE: The changes you make in SITESPECIFIC.CMD should reflect what the configuration will look like after you replace the VAP MCU in the CPU to be upgraded. 9. If any CPU in the kernel will still be at B5 after the FCO is installed in this CPU, proceed to step 10. Copy the microcode files from the [B6] directory to the [UCODE] directory only if all CPUs will be at B6 after the B6 VAP FCO is installed in this CPU. >>>COPY [B6]*.LOD [UCODE]*/LOG >>>COPY [B6]*.DAT [UCODE]*/LOG >>>COPY [B6]*.SYN [UCODE]*/LOG 10. Replace the VAP MCU Turn the system power off by putting the Operator Control Panel power switch in the "Off 0" position. Remove VAP MCU and install new VAP MCU (F6-P1009-AA) REV L02 in accordance with the MCU removal and replacement procedures. This procedure is documented in the VAX 9000 Family System Maintenance Guide, Volume 1 (Document Number EK-KA901-MG). Restore power to the system by putting the Operator Control Panel power switch in the "On 1" position. 11. Verify the new VAP MCU. Where "n" is the CPU in which the new VAP MCU will be installed: >>>SENSE CPU n >>>SHOW CONFIG/RINGS/CPU:n (Verify that no mismatches occur) >>>TEST/SCAN/LOG/TRACE/ISOLATION/CPU:n >>>SET CLOCK/SCU/CPU:ALL OFF >>>TEST/SCU/CPU:n >>>TEST/STRUCTURE/ALL/LOG/CPU:n >>>I/K >>>@[TOOLS]CPUn_ZFLEX >>>I/K >>>SET BOOTSET/PRIMARY=n >>>LOAD [SYSMAINT]EVKAA >>>ST 200 >>>^P >>>HALT/CPU:ALL >>>I/K/B >>>@[CONSOLE]CLEAR_MEMORY >>>SET BOOTSET/PRIMARY=n _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 9 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ Load VDS and run the following MACRO level Diagnostics: EVKAQ EVKAR EVKAS EVKAT EVKAU EVKAV EWKAX EWKMP DS> EXIT >>>HALT/CPU:ALL >>>I/K 12. Boot VMS and run UETP NOTE: While UETP is running, execute ADMIN.CMD for the MCU that was removed from the kernel. Every MCU that is returned must have a TK50 tape created by the ADMIN.CMD procedure. Assuming that the VAP MCU just removed from the kernel was in good working order, it should be clearly identified as; "RETURN FOR UPGRADE". VAX 9000 210/410 configurations: ------------------------------- If the system will be returned to the customer after this phase of the FCO, a 6 hour UETP run is recommended. VAX 9000 4XX multiple CPU configurations: ---------------------------------------- If the system will be returned to the customer after this phase of the FCO, a 6 hour UETP run is recommended. If another CPU is to be upgraded immediately following the UETP test, a minimum of 1 hour of UETP is recommended between CPU upgrades. 13. Go to step 4 if you wish to upgrade another CPU in the kernel. 14. Cleanup DUA50 (only after all CPUs in the configuration have been upgraded to B6). When the B6 FCO has been completed and all CPUs in the kernel are at the B6 revision, you can eliminate files and directories that are no longer required. _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 10 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ NOTE: You may want to retain these files until you are comfortable that the machine is stable as a B6 kernel. DUA50:[SYSMAINT] >>>DELETE [SYSMAINT]XB5*.SPDF;* DUA50:[SYSEXE] >>>DELETE [SYSEXE]B5_SITESPECIFIC.CMD >>>DELETE [SYSEXE]B5_SITEINIT.CMD DUA50:[UCODE] >>>PURGE [UCODE]*.LOD >>>PURGE [UCODE]*.DAT >>>PURGE [UCODE]*.SYN DUA50:[B6] >>>DELETE [B6]*.*;* >>>DELETE [000000]B6.DIR;* 15. Remove workarounds (if implemented) for problems resolved by the B6 VAP FCO. On the SPU's RD54: In [SYSEXE]SITEINIT.CMD Comment out the line "D/CPU=('CPU') CTU.CTMV.SET_SEL_H<1> 1" if not already commented out. !DISABLE SET O !SHUTS OFF HALF OF CACHE !D/CPU=('CPU') CTU.CTMV.SET_SEL_H<1> 1 16. Report this FCO activity on the LARS form in the "Fail Area/ Module/FCO/Comments" column as per the example on page 11. _ _ _ _ _ _ _ | FCO 9XXX-O003 | | | | | | | | | |d|i|g|i|t|a|l| | PAGE 11 OF 11 |_|_|_|_|_|_|_| | | _______________________________|_________________________________________ LARS FORM USA GIA EUROPE Activity - (a)Contract and Warranty W U Y (b)IN-DEC Contract K Hardware Segment Code 111 Non Contract/Non Warranty F F F (b)RTD/Off-site Agreement F Product Line 01 DEC Option 9XXX 9XXX 9XXX Type of Call M M M Action Taken D D I Fail Area-Module-FCO-Comments 9XXX-O003 9XXX-O003 9XXX-O003 Material Used EQ-01610-01 EQ-01610-01 EQ-01610-01 EQ-01610-02 EQ-01610-02 EQ-01610-02 (a) Warranty Optimum, Warranty Standard and Warranty Basic (on-site) Agreements; * Note material (only) free of charge for all customers. (b) Applies to IN-DEC Area Only (c) RTD=Return to Digital or Off-site Agreements; If Field Engineer On-site, use Activity Code "F". \^ 9XXX \\9XXX \\9000 \\FCO_DOCS \\1991 \\APR \\P1009 \\VAP \\MCU