![Digital Equipment VAXft Systems 810 Service Information Download Page 142](http://html1.mh-extra.com/html/digital-equipment/vaxft-systems-810/vaxft-systems-810_service-information_2498646142.webp)
•
CPU module ID EEPROM:
Valid checksum
OpenVMS and firmware status byte is good
Module ID and module name compatible with other zone
Module hardware revision compatible with other zone (major)
Firmware and software revisions compatible with other zone (major)
•
I/O ATM module ID EEPROM:
Valid checksum
OpenVMS and firmware status byte is good
Module ID and module name compatible with other zone
Module hardware revision compatible with other zone (major)
Firmware and software revisions compatible with other zone (major)
•
CPU module data EEPROM:
Valid checksum
System data area must be the same in both zones
•
Memory restrictions for synchronization:
Same memory configuration on both zones
•
Cross-link and resynch cables functional
•
Operational modes must be compatible (that is, burnin state)
•
Ability of the CPU console firmware to run in cross-link in Duplex mode
Table 4–32 lists the test failure codes. Each bit represents the results of checking
the given condition. The test will attempt to check all conditions, and updates the
bits as it performs the test (set bit indicates failure).
Table 4–32 Duplex Compatibility Test Failure Codes
Failure Code
Bit Number
Code Description
00
CPU self-test failed
01
CPU zone test failed
02
CPU system test failed
03
ATM self-test failed
04
Both zones have the same zone ID
05
CPU ID EEPROM is bad
06
CPU ID EEPROM OpenVMS status field shows module is bad
07
CPU ID EEPROM firmware status field shows module is bad
08
CPU ID EEPROM module type field mismatches between zones
09
CPU ID EEPROM module name field mismatches between zones
10
CPU ID EEPROM hardware revision (major) mismatches between
zones
11
CPU ID EEPROM firmware revision (major) mismatches between
zones
(continued on next page)
4–58 Error Handling and Analysis