Table of Contents
Advertisement
Chapter 4: Troubleshooting Procedures
Be aware that the Micro-CS can only boot another Micro-CS that has the
same configuration. Thus, a Micro-CS with only 2MB of RAM and no
option keys enabled cannot boot a Micro-CS with 4 MB of RAM and the
IPX option enabled.
A Micro-CS that has been reconfigured as a load server host, but not
rebooted, cannot boot another Micro-CS on the network. Rebooting the
Micro-CS load server host ensures that the parameters are set.
4.6
MICRO-CS DUMPS
The Micro-CS dumps its memory image to a host running load server
software when certain software or hardware events occur. Events that
trigger Micro-CS dumps are
•
Non-recoverable hardware or software errors.
•
Software fails to reset the Micro-CS's watchdog timer.
•
Software fails one or more internal consistency checks.
•
Hardware detects an internal fault.
Dump files are generated for use by technical support
NOTE
personnel only.
Activity
Dump
Key:
= On continuously
The Micro-CS sends a dump file to a preferred load dump host. If you do
not define this host by specifying an address, the Micro-CS broadcasts a
request and dumps to the first host running erpcd daemon that responds.
The dump creates a file in the dump host's directory, named
/usr/spool/erpcd/bfs, and assigns a unique file name for each Micro-CS
but not for each crash dump. For each dump, the Micro-CS overwrites the
existing file.
4-12
Table 4-8 Indicator States during a Dump
STATUS
ATTN
green
amber
= Flashing irregularly
Micro-CS Installation Guide
NET
green
Advertisement
Table of Contents
