Table 27. A00-FF0 through A24-xxx SRNs (continued)SRN Description FRU/actionA02-06x Memory Data error (Bad data going tomemory). 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A02-09x System bus parity error. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A02-10x System bus time-out error. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A02-11x System bus protocol/transfer error. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see“POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A02-12x I/O Host Bridge time-out error. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A02-13x I/O Host Bridge address/data parityerror. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A03-00x Error log analysis indicates an errordetected by the I/O device, but thefailure could not be isolated.1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.A03-01x I/O Bus Address parity error. 1. Check the BladeCenter management-moduleevent log; if an error was recorded by thesystem, see “POST progress codes(checkpoints)” on page 84.2. If no entry is found, Replace thesystem-board.Chapter 2. Diagnostics 159
