POST error messages

The following table describes the extended POST (Power-On Self-Test) error messages that might appear on the system console if your appliance encounters CPU-level system errors during the POST process.

Note
Always power-cycle your appliance when you receive any of the following errors. If the system repeats the error message, follow the corrective action for that error message.

Error message or code	Description	Corrective action
[RAMX]	No physical memory was found by the system.	This indicates that the system doesn't see any memory. Try reseating the DIMM. See Replacing the SDRAM DIMM on the CPU module.
[Cerr]	Cache error.	These are cache errors. These errors indicate a bad CPU. If a power-cycle doesn't fix the problem, replace the CPU module. See Replacing the CPU module.
[Cer2]	Cache error.
[EXC!]	Exception.	This indicates that the system took an exception while in firmware. If it is repeatable, this is likely a software bug in the firmware. Contact Network Appliance and provide a log of the error. If you can't get past this error, boot the system using the backup firmware image.
[RUN!]	CFE (common firmware environment) is jumping to executable code.	This is not an error but rather a progress state indicator used to help troubleshoot the problem.
[HELO]	Very early Init code.	If the system stops on one of these error codes, there is likely a hardware problem. First, try Step 1 below. If this doesn't fix the problem, proceed to the subsequent steps until the problem is fixed. Power off the system, then power back on. Try booting with the backup firmware image. See Booting your appliance from a backup firmware image. Replace the CPU module. See Replacing the CPU module.
[L1CI]	L1 cache INIT.
[L2CI]	L2 Cache INIT.
[TST1]	Simple POST test: cache of both levels and tags.
[CPU1]	CPU1 INIT.
[cpu1]	CPU1 entering IDLE loop.
[DRAM]	Running on CPU0, on memory segment 0 (that is, program is now running in RAM rather than flash memory).	If the system stops on one of these error codes, the memory is bad or the NVLOG subsystem malfunctioned. To test this, reseat the DIMM and disconnect the battery. See Replacing FAS270/270c Devices. If that fails to clear the problem, replace the DIMM. See Replacing the SDRAM DIMM on the CPU module.
[Zero]	Zero memory...no nvmem.
[Keep]	Keep memory...preserve nvmem.
[ZBSS]	Zero the BSS segment.
[CODE]	Zero and copy the code segment from flash to memory.
[DATA]	Zero and copy the data segment from flash to memory.
[RELO]	Jump to the new code segment.
[L12F]	Flush and enable caches.
[MAIN]	Jump to the main CFE memory.
[KMEM]	Initialize CRDs heap.
[NVCL]	Clear memory that isn't owned by NVMEM or CFE.
[CONS]	Attach console device.	Check the connection between your appliance and the console device. Replace the cable if it is defective.
[CIOK]	Copy right etc.	A message of this type doesn't indicate a specific failure, but a general failure of some system component. Try booting with the backup firmware image. See Booting your appliance from a backup firmware image. Otherwise, replace the CPU module. See Replacing the CPU module.
[AREN]	Physical memory map INIT.
[DEVI]	Misc devices INIT.
[ENVI]	Environmental variable subsystem INIT.
[PCIH]	PCI host bridge INIT.	If the system stops with one of these error codes, there is likely a problem with either the SB1250 chip or the ISP2312 FC-AL chip. Try booting with the backup firmware image. See Booting your appliance from a backup firmware image. Otherwise, replace the CPU module. See Replacing the CPU module.
[PCIB]	PCI try to init P2P bridges.
[PCIS]	PCI device scan.
[CFE ]	This message is written when CFE jumps to the exception handler, for whatever reason. This is caused by either bad hardware or a bad flash memory.	Power-cycle the system. Try booting with the backup firmware image. See Booting your appliance from a backup firmware image. Replace the CPU module. See Replacing the CPU module.