Dell Force10 E300, Configuration Manual, Page: 1207 / 1262

E-Series TeraScale Debugging and Diagnostics | 1207
The three CPUs use Fast Ethernet connections to communicate to each other and to the line card CPUs
using Inter-Processor Communication (IPC). The CP monitors the health status of the other processors
using heartbeat messaging exchange.
FTOS automatically saves critical information about the IPC failure to NVRAM. Such information
includes:
• Status counters on the internal Ethernet interface
• Traffic profile of the inter-CPU bus
• Kernel drops
• High CPU exception conditions
Upon the next boot, this information is uploaded to a file in the CRASH_LOG directory. Use the following
command sequence beginning in EXEC mode to capture this file for analysis by the Dell Force10 TAC.
Message 6 CP monitor
%RPM1-P:CP %IPC-2-STATUS: target rp2 not responding
%RPM0-S:CP %RAM-6-FAILOVER_REQ: RPM failover request from active peer: Auto failover on failure
%RPM0-S:CP %RAM-6-ELECTION_ROLE: RPM0 is transitioning to Primary RPM.
%RPM0-P:CP %TSM-6-SFM_SWITCHFAB_STATE: Switch Fabric: UP
Step Task Command Mode
1 Display the directories in flash memory. The output
should include:
1 drwx 2048 Jan 01 1980 00:00:06
CRASH_LOG_DIR
dir flash: EXEC
2 Change to the CRASH_LOG directory. cd CRASH_LOG_DIR EXEC
3 View any saved files in the CRASH_LOG
directory. The naming convention is:
sysinfo_RPMIDProcessorID _ timestamp
For example:
sysinfo_RPM1CP_20060616_013125
sysinfo_RPM1RP1_20060616_013248
sysinfo_RPM1RP2_20060616_013249
dir EXEC Privilege
4 View the contents of the file. show file flash://CRASH_LOG_DIR/
[file_name]
EXEC Privilege